Monday, December 1, 2014

HOW TO CHANGE DATE FORMAT

Q. - HOW TO CHANGE DATE FORMAT
ANS - GO TO OY01 > CHANGE HERE DATE FORMAT

HOW TO DISPLAY VALUES IN INR RUPEES FORMAT

Q. -- HOW TO DISPLAY VALUES IN INR / RUPEES FORMAT
ANSWER : -- GO TO OY04 >  ASSIGN 3 DECIMAL WITH INR > SAVE



Thursday, September 25, 2014

TREE TURN OFF IN FB60, FB50, FB70

1. Manual Tree Turn Off
2. Edit > Screen Variant > Reset Screen Variant.

Thanks

Monday, August 25, 2014

SAP COMMAND FIELD

-- Command field --

You can execute the following commands in this field with Enter:
  • To call a transaction
    • in the same session (window)
      Enter: /nxxxx (xxxx = transaction code).
    • in the same session (window), whereby the initial screen is skipped.
      Enter: /*xxxx (xxxx = transaction code).
    • in an additional session,
      Enter: /oxxxx (xxxx = transaction code).
  • To end the current transaction
    Enter: /n.
    Caution: Unsaved changes are lost without warning
  • To delete the current session.
    Enter: /i.
  • To generate a session list
    Enter: /o.
  • To end the current transaction and return to the starting menu
    Enter: /ns000.
  • To log off from the system
    Enter: /nend.
  • To log off from the system without a confirmation prompt
    Enter: /nex.
    Caution: Changes that were not saved are lost without warning.

Saturday, July 19, 2014

SAP NOTES   143439 - WBS scheduling with 'Adjust basic dates'

Symptom
When you schedule WBS elements, operations receive dates based on the old basic dates although
indicator 'Adjust basic dates' is set and the old basic dates are not retained.

Other Terms
CJ2B, WBS scheduling, CJ21, network scheduling

Reason and Prerequisites
This is caused by a program error.

Solution
Repair the source code;
Release 3.0A - 4.5A: also implement Notes 130305 and 134237.

SAP NOTES 151551 - Consulting: Scheduling of network

Symptom
The result of the network scheduling is not clear.
The system does not display the capacity requirements calculated by scheduling correctly.

Other Terms
CN21, CN22, CN24, network, scheduling, check list, scheduling of overall network, capacity
requirements, basic date, activity date, shift, relationship, night shift

Reason and Prerequisites

Solution
Check your settings according to the questions listed below:



Check list
* Note the following general rules
Networks are generally scheduled both forwards and backwards. The scheduling type defines which
scheduling direction the system takes into account first.
The dates of the earliest dates result from forward scheduling. The dates of the latest dates result
from backward scheduling.
* Which set of dates is used for scheduling?
Check which set of dates is selected.
* Which results cannot be explained?
1. Basic dates/forecast dates
2. Activity dates
3. Capacity requirements 
1. Basic dates/forecast dates

* Do the basic dates change?
Check whether the alternative 'Adjust basic dates' has been chosen for the scheduling parameters. In
this case, the subsequent backward scheduling is executed from the scheduled finish date for
scheduling type forward. In the case of scheduling type backward, the system schedules from the
scheduled start date or if a "today" scheduling is to be executed, it schedules from the current
date.
If indicator 'Adjust basic dates' is not set, forward and backward scheduling is executed from the
entered basic dates. If no basic date is specified, the respective scheduling is executed from the
scheduled date.
Check whether the basic dates are set correctly on the basis of the activity dates.
* Is it possible to explain the basic dates on the basis of the activity dates?
1. Yes: The problem is caused by the activity dates. Proceed with the questions listed under "2.
Activity dates".
2. No: Continue.
* Has a "today" scheduling been executed?
Check the scheduling log for this.
Note that the forward scheduling is automatically overridden by a "today" scheduling as soon as the
order start date lies further in the past than the number of days defined in Customizing. In the
network, you can also maintain online the number of the days allowed in the past.If no order start date is defined, a "today" scheduling is executed provided the scheduled start
date lies too far in the past.
* Are activities already finally confirmed?
Basic dates are only adjusted allowing for the dates of not yet finally confirmed activities.
The system does not redetermine any dates for finally confirmed activities but copies the actual
dates to the activity dates.
* Are night shifts assigned to the last activities relevant to scheduling?Yes: Note that for backward scheduling the finish date is the end of the night shift of the previous
day so that, in this respect, the order finish date can be moved by one day. As a result, the
production dates can fall on a day that is a day off according to the factory calendar.
2. Activity dates

* Are the durations of the activity segments correct?
1. No: Go to point 2.1 'The durations of the activities are not correct'.
2. Yes: Go to point 2.2 'The durations of the activities are correct. However, the individual dates
cannot be explained.'
2.1. The durations of the activities are not correct

* Check both the formula for calculating duration in the work center and the standard
values used in the order.
l Which variables are used for the formulas?
l How is the result calculated?
l Using Transaction CR04, try to reproduce the problem for the operation stored in the work
center. With this transaction, you can test the scheduling formulas of the work center. To do
this, enter both the general operation values and the standard values and execute scheduling
(F5).
* Are the activities already finally confirmed?
Finally confirmed activities are no longer scheduled. The actual dates are copied to the activity
dates. The durations are calculated from the actual dates.
* Are activities already partially confirmed?
For partially confirmed activities, the remaining duration is scheduled during forwards scheduling
after the confirmed actual dates. The earliest start date is calculated from the confirmed actual
start date. The earliest finish date is the same as the actual start date plus the forecasted
processing time. If when you confirm, you have maintained a finish date for the forecast, scheduling
adopts the finish date for the forecast for the earliest finish date. If there is neither a
forecasted duration nor a forecasted finish date, the system then takes the planned duration
(benchmark) as a starting point and adds it to the actual start date.
The latest dates are not adjusted to the 'actual' situation. The activities - from the start date of
the successors - are scheduled backwards with the remaining duration - for the latest start and
finish date , so that the buffers can be calculated for the activity.
Exception: If indicator 'Shift order' is activated, the earliest dates are only scheduled with the
remining duration, the actual dates of the partially confirmed activities are not taken into
account.
* Are the activities relevant to scheduling?
For this check the activity control keys.
Note that for activities not relevant for scheduling, the system does not check whether the activity
falls on a day off since the activity can always be executed directly before or after another
activity. The duration of activities not relevant to scheduling is 0.
* Is the activity replaced by a subnetwork?
If according to the control key the activity is not relevant to scheduling, the activitiy is
replaced by the subnetwork when an overall network is scheduled so that the duration of the
subnetwork is copied to the activity.
If the activitiy is relevant to scheduling, the duration of the subnetwork is not copied to the
activity duration.
* Is it an externally processed activity?
If the activity is defined as an externally processed activity, the system displays the planned
delivery time as processing time and takes it into account. The activity is scheduled with the
planned delivery time according to the Gregorian calendar.
Note that activities with the 'Internally processed operation /external processing possible'
characteristic stored in the relevant control key are not interpreted as externally processed
activities.
* Is it an activity element?
The activity element dates are calculated on the basis of their earliest/latest dates for the
activity; in this case, the stored offsets are evaluated for the start and end. The duration defined
by the found dates is stored.
* Can the activity be extended?
Yes: The activity is extended according to the duration of the free float.
* Are the floats of the activity correct?
Check the floats using the dates of predecessors and successors.
* Has a reduction been executed during scheduling?
Check the scheduling log or the 'Reduction' field in the order header screen.
l Yes: Check the reduction parameters of scheduling and the scheduling log.
           Check whether the duration of the in-house production has been calculated correctly
according to the reduction.
           Check whether the duration falls short of the minimum duration of the activity. This
might be caused by the reduction. In this case, the duration is set to the minimum duration.
2.2. The durations of the activities are correct, however, the individual dates cannot be
explained.

In general, activities and relationships are scheduled using the operating time of a stored work
center. If no work center is stored but a factory calendar, it is scheduled to the day using the
factory calendar. If neither work center nor factory calendar are stored, it is scheduled according
to the Gregorian calendar.
* Have relationships been maintained?
Here note the time-dependent relationship representation in the network structure overview if
necessary.
l To which category does the relationship belong? Which activity is the predecessor, which one is
the successor?
l Has a duration of the relationship been maintained?
l Do external relationships exist for activities of other networks?
           In this case, the system takes the dates of the external activities as restriction dates
into account. Here, the external network is not scheduled unless you started scheduling of the
overall network.
* Is the activity dispatched?
Check the status of the activity, and if necessary, the dispatching dates.* Have restriction dates been maintained for the activity?Check the type of the restriction dates and check whether the activity dates are correct on account
of the restrictions. Note that the restriction dates must always be taken into account unless the
activity is dispatched or finally confirmed.
* Is the activity assigned to a WBS element?For this, check the assignments of the activities (for example, on the general overview of
activities).
The dates of the WBS element are adhered to if the element is determining the dates, that is, if
indicator 'Network scheduling' is not activated in the WBS element. If indicator 'Network
scheduling' is activated in the WBS element so that the network determines the dates, the system
does not take the WBS dates into account.
If the operation is dispatched or if finally confirmed or restriction dates have been maintained,
this is not valid.
* Does the time unit of the activity or the relationship corresponds to the unit day or is
it even larger?
1. Yes: Go to point 2.2.1.
2. No: Go to point 2.2.2.
2.2.1. The time unit is larger or or equal to day
2.2.1.1. A work center is stored for the activity or relationship.
Note that the dates determines are moved to the next respective productive date, allowing for the
capacity at the work center.
* Does an active version of the available capacity exist?
* Yes: Scheduling is executed to the day using the days on which shifts are defined.           If no operating time is maintained for the specified period, the system schedules
according to the Gregorian calendar.
*No: Continue.

* Has a factory calendar been stored in the work center?
l Yes: Scheduling is executed to the day using the workdays of the factory calendar.
l No: Scheduling is executed using the Gregorian calendar.

2.2.1.2. No work center but a factory calendar is stored for the activity or relationshipScheduling is executed to the day using the workdays of the factory calendar

2.2.1.3. For the activity or relationship, neither a work center nor a factory calendar is
stored
Scheduling is executed according to the Gregorian calendar.

2.2.2. The unit of the activity segment is smaller than day

2.2.2.1. For the activity or relationship, a work center is stored
* Does an active version of the available capacity exist?
l Yes: Has a shift sequence been stored?
¡ No: It is scheduled using the shifts stored in the interval of available capacity; in this
case the planned breaks are distributed equally over the entire shift duration.
¡ Yes: Check whether work break schedules are stored in the shift definitions of the shift
sequence and whether the 'Scheduling allowing for breaks' indicator is activated in
Customizing of the scheduling parameters.
                    If work break schedules are stored in the shift definitions of the shift
sequence and the 'Scheduling allowing for breaks' indicator is activated, the system schedules using
shifts stored in the interval of available capacity, while in doing so the breaks are taken
permanently into account.
                    If this is not the case, the system schedules using the shifts stored in the
interval of available capacity, while in doing so the planned breaks are distributed equally over
the entire shift duration.
* No: Has a standard available capacity been stored?
¡ No: It is scheduled according to the Gregorian calendar.
¡ Yes: If a factory calendar is stored, scheduling is executed using the standard available
capacity and the workdays of the factory calendar, while in doing so the breaks are
distributed equally over the entire shift duration.
                    If no factory calendar is stored, scheduling is executed using the standard
available capacity and the workdays of the plant calendar, while in doing so the breaks are
distributed equally over the entire shift duration.
The problem exists also when these rules are taken into account
           Before you enter a customer message, try to reproduce the problem for the activity stored
in the work center using Transaction CR04. With this transaction, you can simulate scheduling using
a work center. For this purpose, you can on the one hand, specify the start or end of the productive
time as well as a duration so that the missing date is determined with regard to the shifts of the
work center. On the other hand, with regard to the shifts, the productive time between the dates can
be calculated by specifying the two dates and an initial duration. Start for the two simulation
types the determination of productive time (F8) and take the 'Breaks' indicator into account for
scheduling allowing for breaks.
           
2.2.2.2. No work center but a factory calendar is stored for the activity or relationship.Scheduling is executed using the workdays of the factory calendar
2.2.2.3. For the activity or relationship, neither a work center nor a factory calendar is
stored
Scheduling is executed using the plant calendar

3. Capacity requirements

Capacity requirements are calculated during scheduling. The dates of the respective operations are
copied to the dates of the capacity requirements. Changes relevant to scheduling (for example,
changes to the lot size) are only copied to capacity requirements after another scheduling.
In the network, check the procedure detail screen 'Person assignment' in order to check whether
capacity requirements have been generated for this activity. You can receive a detailed display and
an evaluation of the capacity data in the capacity requirements planning. You can branch directly
from the network to graphical capacity requirements planning.
3.1. The system displays capacity requirements for a capacity category.
* Is the amount of the capacity requirements correct ?
Yes: The result is correct
l No: Check the following points:
¡ Check the work for the activity and the formula for the capacity categories for the work
center.
¡ If necessary, test the formula at the work center with the work you maintained for the
activity.

* Does the system display capacity requirements for all relevant capacity categories?
l Yes: The result is correct
l No: Check the capacity categories exsiting for the work center

3.2. Detail screen 'Person assignment' does not exist although capacity requirements ought
to be calculated

* Have you set the 'Capacity requirements' indicator in the 'Scheduling' header screen of
the network?
l No: Set this indicator and schedule again. If still no capacity requirements exist afterwards,
continue. The 'Capacity requirements' indicator is copied from the settings of the Scheduling
Customizing to the network header. If you basically want to have capacity requirements
calculated, change your Customizing correspondingly.
l Yes: Check the following points:
¡ Check the work entered for the activity.
¡ Check the formula used for capacity category at the work center and test the formula at the
work center with the value of the work used for the activity if necessary.
¡ Check the control key used. If the control key of activity does not support any capacity
requirements planning, the system does not calculate any capacity requirements.
¡ Check the status of the activity. Is the activity partially or finally confirmed? Finally
confirmed activities have no longer any capacity requirements.

3.3. The system displays capacity requirements although no capacity requirements ought to
be calculated

You can deactivate the capacity requirements planning in different ways. If you want the system to
calculate no capacity requirements for the entire network, deactivate the 'Capacity requirements'
field in the header of the network. If you want the system to calculate never any capacity
requirements, change your Customizing correspondingly so that the 'Capacity requirements' indicator
is always inactive.
If you only want the system to calculate no capacity requirements for individual activities, choose
a corresponding control key for this activity or use a work center without capacity categories.

4. The result can also not be explained after the stated points have been checked

Before you enter a customer problem message:
l Search for notes in the Online Service System
           Search for notes of your release for the components PP-CRP-SCH (scheduling) and PS-DAT-
NET (network scheduling). Do not mention key word 'scheduling' because this key word is already
sufficiently defined by the component allocation. For the search, use additional key words which
characterize your problem or which characterize the data to be scheduled in more detail, for
example: Basic dates, activity dates, night shift, scheduling of overall network ...
l If you cannot find a note that solves your problem, create a customer problem message for the
PP-CRP-SCH or PS-DAT-NET component. Answer the following questions in your problem description:
           1. What does your problem look like?
                    For this, restrict your problem as far as possible with this check list.
           2. Where and when does your problem occur or can the problem be reprocessed?
¡ If possible, make example data available and describe how your problem can be reprocessed.
¡ If your problem can be restricted to the scheduling of one activity, try to reproduce the
problem for the work center stored in the activity using Transaction CR04.
                    With this transaction, you can simulate scheduling using a work center. For this
purpose, you can on the one hand specify the start or end of the productive time as well as a
duration so that the missing date is determined with regard to the shifts of the work center. On the
other hand, with regard to the shifts, the productive time between the dates can be calculated by
specifying the two dates and an initial duration. Start for the two simulation types the
determinatin of productive time (F8) and take the 'Breaks' indicator into account for scheduling
allowing for breaks.
                    Furthermore, you can test the scheduling formulas of the work center with this
transaction. For this enter the general activity values as well as the standard values and execute
scheduling (F5).
In the same way as for scheduling formulas you can test the formulas which are
the basis for the capacity requirement calculation (F6) and costing (F7).
           3. What other determining factors exist ?
                    For example, Customizing parameters scheduling type, relationships.
                    

SAP NOTES 188565 - Earliest and latest dates after WBS scheduling

Symptom
You carry out a WBS scheduling. For this indicator "Adjust basic dates" is activated. Operations of
a network are assigned to different WBS elements.
Earliest and latest dates of the operations then can differ heavily or the calculated basic dates of
the WBS elements can be incorrect, if relationships in other WBS elements exist within a WBS
element.
 
Other Terms

CJ2B, WBS, project planning board, FLG_WBS

Reason and Prerequisites The problem is caused by a program error.

Solution
Implement the program correction.
Note that for a scheduling with indicator "Adjust basic dates", the calculated dates of the WBS
elements are considered as restrictions to the respective operations also when the indicator
"Network scheduling" (Network determines dates) is activated. If you carry out a forward scheduling
with alternative "Adjust basic dates", an end of the WBS element is calculated that acts as a
restriction to the operations during the following backward scheduling.Similarly, the connectivity for a backward scheduling and the calculated start date of the WBS
element are valid.

The changes of the two related Notes 113062 and 130305 are cancelled by the change described in the
"Corrections" section. By these two notes the calculated WBS dates are not to be interpreted as
restriction if relationships between different WBS elements exist. However, this can cause
inconsistent behavior for scheduling so that these corrections must be cancelled.
If, in your process of WBS scheduling in which the network determines dates, you do not want the WBS
dates to be considered as restrictions,refer to related Note 155494. This can be treated as a
preliminary development, since as of Release 4.6 the WBS dates are not considered as restrictions
for a WBS scheduling with indicator "Network scheduling" any more. Hence, as of Release 4.6 the WBS
scheduling of alternative "Network scheduling" acts similarly to a scheduling of the overall
network.
 

SAP NOTES 134237 - WBS scheduling with 'Adjust basic dates'

Symptom
When scheduling WBS elements, the basic dates of the WBS elements influence the operation dates
although indicator 'Adjust basic dates' is set and the operations have neither successors or
predecessors.
 
Other Terms
CJ27, CJ2B, CJ2D
 
Reason and Prerequisites
The problem is caused by a program error.
 
Solution
Repair the source code.

SAP NOTES 155494 - Advance development: Scheduling WBS elements

Symptom
Scheduling WBS elements with set indicator 'Network scheduling' does not adjust the dates of the WBS but considers them as restriction dates for the activities of the networks.

Other Terms
Project planning board, restriction, WBS dates

Reason and Prerequisites
In Release 4.6, the logic has changed.

Solution
Advance development as modification:
If you chose alternative network scheduling for project scheduling, the WBS dates are no longer considered as restriction dates for the activities.

Execute the specified source text changes, and include the following import parameter for function module CX_INIT_SCHEDULING:
Parameter name   Reference type   Proposal     Optional  Pass value I_FLG_NETZ_PSP    CX_BOOL          SPACE          X         X

In advance, consider Note 143439 as well as Note 134237 in Releases earlier than Release 4.5B.

SAP NOTES 188565 - Earliest and latest dates after WBS scheduling

Symptom
You carry out a WBS scheduling. For this indicator "Adjust basic dates" is activated. Operations of a network are assigned to different WBS elements.
Earliest and latest dates of the operations then can differ heavily or the calculated basic dates of the WBS elements can be incorrect, if relationships in other WBS elements exist within a WBS element.

Other Terms
CJ2B, WBS, project planning board, FLG_WBS

Reason and Prerequisites
The problem is caused by a program error.

Solution
Implement the program correction.

Note that for a scheduling with indicator "Adjust basic dates", the calculated dates of the WBS elements are considered as restrictions to the respective operations also when the indicator "Network scheduling" (Network determines dates) is activated. If you carry out a forward scheduling with alternative "Adjust basic dates", an end of the WBS element is calculated that acts as a restriction to the operations during the following backward scheduling.
Similarly, the connectivity for a backward scheduling and the calculated start date of the WBS element are valid.

The changes of the two related Notes 113062 and 130305 are cancelled by the change described in the "Corrections" section. By these two notes the calculated WBS dates are not to be interpreted as restriction if relationships between different WBS elements exist. However, this can cause inconsistent behavior for scheduling so that these corrections must be cancelled.

If, in your process of WBS scheduling in which the network determines dates, you do not want the WBS dates to be considered as restrictions,refer to related Note 155494. This can be treated as a preliminary development, since as of Release 4.6 the WBS dates are not considered as restrictions for a WBS scheduling with indicator "Network scheduling" any more. Hence, as of Release 4.6 the WBS scheduling of alternative "Network scheduling" acts similarly to a scheduling of the overall network.

Thursday, July 10, 2014

Creating a SAP mail distribution list

Transaction code SO23
X Shared distribution lists
Name : ZXXXX
Title : XXXXX Mail Distribution
Don't enter anything in the Folder field.
Folder : Click the down arrow
Next screen :
Folder Name : ZXXXX
Folder Title : Mailing address
Folder Area : Shared
Click Create Folder
Next screen : 
Indexing : Tick
Specify the 'Retention period of a document in this folder (days)'.
Choose the 'Folder access authorization'.
Finish, click the Enter button.
Click the tabstrips 'Distri. list content' to type in your mailing list.
Save your entries.
Finally, test it by sending a mail via the distribution list ZXXXX.

Monday, June 30, 2014

No G/L account has been specified for T /INR for the bank Message no. FZ018

This has to do with account dtermination in FBZP. Check if for payment method T and currency INR, you have G/L account defined.


OR


Please confirm which bank account you had specified in vendor master.
 

Customer/vendor does not have suitable bank details for pmnt method T

To execute APP succesfully you should maintain bank details in your vendor master data.
T.Code: FK02
go to payments transaction tab and maintain the bank details like Ctry, bank key, bank account no.

FZ003 : Company codes &/& do not appear in proposal & &; correct

Reasons :
- no line items
- config miss
- There will be no dues as of that run date..now post an invoice today and run payment tomorrow date provided payment terms should be payment immediately..

if u really want to run then change the payment terms and check wheter it is due for payment then run APP.
- This is normal issue for this issue delete the all uncompleted proposals,
check the run date dropdown button,there uncompleted proposal(yet to be payment completed)available May be those invoice stored in that proposals

Path:Menu>Edit>Proposal>Delete

After selecting the RUN DATE and IDENTIFICATION.
Please go to EDIT TAB
STEP 1) EDIT-->PAYMENTS-->DELETE OUTPUT.
STEP2) EDIT-->PROPOSAL-->DELETE.
STEP3) EDIT-->PARAMETERS-->DELETE. If this option is active.


- First check whether the Vendor is blocked in any other incomplete Payment run - proposal is created but it is not completed.
Further, in transaction code FBZP in the tab Bank Selection check the ranking order. Also check the Bank accounts.
The best to analyze the problem is to read the log as it will give the details where exactly it is failing. So in the parametrs select the log check boxes.
- The proposal run date and the next date are to be checked for each of the earlier APP Runs that are not posted. Ensure that there are no duplications.
The second most important point is that as long as the proposal is pending the items are locked for further processing. Hence delete all the earlier payment runs which are not posted and pending. The parameters and the proposal are to be deleted for each of the pending payment runs.


Also please check payment Term...

Friday, June 20, 2014

In company code XXXX, the number range 10 is missing for the year 20XX

Document type --> Document numebr range --> Document number series maintained for the present fiscal year..

Go to OBA7, select your document type.. It must have got 10 in the numebr range ... Click on number range information and create the series for number range 10..

SAP FI - PP Integration

FI-PP integration takes place mainly at these stages-

1) When you create and release the production order, the planned costs will be calliculated from BOM and Routing/Master Recipe master data.-Co document will be generated for Planned postings

2) When you issue goods(Raw materials) to production (against Production order) the FI and CO entries will get generated -CO27
FI Entry- Consumption A/C Dr
                   To Inventory A/C Cr
CO primary cost postings will be triggered against the cost center.

3) When operations in routings are confirmed , the cost centers in the work centers will be charged with the activity costs
Here secondary cost postings will be triggered in the production cost centers.

4) After final confirmation of the operations, the GRN will takes place against the production order, here also CO and FI documents will be generated -CO11
FI-Entry-
Finished Goods A/C Dr
  To cost of goods produced A/C

5) If the production order is not confirmed fully, we have to run WIP at the month end-KKAO
FI entry- WIP A/C Dr
               To Change in WIP A/ c Cr
The above entry will be reversed at the time of settlement of production order.

6) When the PO is technically completed, then settlement of PO takes place-K088
FI entry-
Price Difference(Goods) A/C
   To cost of goods produced A/C

Source : http://scn.sap.com/thread/694289
 

Wednesday, February 19, 2014

System status LKD is active ( ORD xxxxxxxxx)

If above error msg has comes during MIRO, then unlock your order via. KO02.