Delta changes between 4.6 c and ECC 6.0 in MM module

    1. BAdI for deductible payable (new)
    2. Requirement prioritizations (new)
    3. Enterprise structure
      (a)Transaction OX18 replaced by views (changed)
      (b) Transaction OX17 replaced by views
      (changed)
      (c) Transaction OX18 replaced by views
      (changed)
    4. Forecast with alternative historical data
    5. Purchasing
      (a) Principle of prudence for credit memos in purchasing (new)
      (b) Mass maintenance of outline agreements
      (c) Commitment plan for purchase contracts (new)
      (d) Availability check in enjoy purchase order and requisition ( changed)
      (e) Product substitution with ATP check for STO
    6. External services
      (a) Putting service items in the purchase order on hold (changed)
      (b) Service based commitments in purchasing (new)
      (c) IR before GR for services in purchasing
    7. Inventory management
      (a) Assignment test (new)
      (b) New movement types in inventory management
    8. Logistic invoice verification
      (a) Variance type as sort criterion for invoice items (new)
      (b) Prepayment of invoices (new)
      (c) Automatic settlement of planned delivery costs (new)





Your Ad Here

Change of Account type from Balance Sheet to P&L account

There are times you commit mistakes in creating general ledger account master record. Instead of creating it as P&L account sometimes it's created as Balance Sheet account (& vise-versa). More often than not, that mistake of g/l account setting becomes apparent only and notice when there are already posted transactions to the account. The SAP standard won't allow change of g/l account from P&L account to Balance Sheet account if transactions exist with the account.

Error Message:

When trying to change, the error message that appear  is " Change balance sheet control in spite of account balance".

Analysis and Diagnosis:

You've changed the G/L account from a "balance sheet acount" to a "P&L account" or conversely.

The g/l account that has changed from P&L account to balance sheet account (& vise versa) has an existing transaction balance.

Soluation:

The message is under application area FH. You can set as warning message applicable to all users (user name is blank), for online processing and/or for bakground processing. The save the change.

In your testing after the change, the message "Change balance sheet control in spite of account balance" is now only a warning message, hence; you can save the change in g/l account from P&L account to Balance Sheet account or conversely.

And always run Balance Carryforward (FAGLGVTR) transaction after the change to classify correctly the balance of the g/l account changed.

In the standard SAP, the message "Change balance sheet control in spite of account balance" is set as an error message. Hence, if this message appear you can not save the change.

As an alternative solution, you can change the message control from an Error (E) to Warning (W) message only. To do that follow this useful guide and procedures:

Path: SPRO → Controlling → General Controlling → Change Message Control.

Transaction Code: OBA5

The message is under application area FH. You can set as warning message applicable to all users (user name is blank), for online processing and/or for bakground processing. The save the change.

In your testing after the change, the message "Change balance sheet control in spite of account balance" is now only a warning message, hence; you can save the change in g/l account from P&L account to Balance Sheet account or conversely.

And always run Balance Carryforward (FAGLGVTR) transaction after the change to classify correctly the balance of the g/l account changed.

source: sap-knowledge.com 

Currency type in FI & CO

1.      Possible currency types in CO

o        10 company code currency

o        20 currency of the controlling area (known only in CO)

o        30 group currency

o       40 hard currency

o       50 index-based currency

o       60 global company currency

2.      Possible currency types in FI:

o        10         company code currency

o        30         group currency

o        40         hard currency

o       50         index-based currency

o       60         global company currency

3.      Some Points on Currency type:

o        A maximum of two currencies can be managed for all postings in FI and CO, independent of the currency types used in the controlling area.

o        Currency type 10 is always managed in FI. In addition, if needed, currency type 30 can be managed as a parallel currency in FI.

o        Currency type 30 can be managed as a parallel currency in FI.

o        Currency type 20 cannot be managed as a parallel currency in FI (this exception is only valid for currency type 20, since it can only be managed in CO).

o        You can also activate type 20 in FI-SL and Profit Center Accounting.

o        There is also currency type 80 (ledger currency) in FI-SL and currency type 90 in Profit Center Accounting (currency of Profit Center Accounting).

o        In FI, a maximum of 3 parallel local currencies can be managed per company code but category 10 is mandatory.

o        You can invariably use all of the currency types with the material ledger.

o        You can only use transfer prices with currency type 10 or 30, since currency type 20 is not supported in FI.

The selection of the currency type in the controlling area has no influence on CO-PA. You can set the operating concern currency independent of the other CO currencies. In the costing-based Profitability Analysis, you can update the operating concern currency and the company code currency (optional). In the account-based Profitability Analysis, the data (as in CO as well) is always updated in controlling area currency, company code currency and transaction currency.

Valuated and non-valuated Sale Order scenarios - Business Process Flow – FI/CO

SAP Scenario 1 - Valuated Sale Order Stock – with Sale Order Controlling – (MTO, ATO and ETO with VC):

 

  1. Enquiry
  2. Opportunity
  3. Quotation (Creation and Approval). In case of ETO – BPO is created and updated in quotation (condition type)
  4. Creation of Sale Order
  5. MRP Run – Creation of Planned Order – Creation of Production Order and Purchase Order
  6. External Procurement – Goods Receipt:

      ROH Inventory Account           Dr (BALANCE SHEET)

To GR/IR Account                   Cr (PROFIT & LOSS ACCOUNT)

 

  1. Material Consumption to Production Order:

In FI:

 

ROH consumption Account       Dr (PROFIT & LOSS ACCOUNT)

To ROH Inventory Account       Cr (BALANCE SHEET)

 

Same in the case with HALB

 

In CO: Cost of Material is debited to Production Order

 

  1. Activity Consumption to Production Order:

 

    • In FI: No Posting
    • In CO: Production Order is debited and cost center is credited with activity cost.

 

  1. Goods Receipt from Production Order:

      FG Inventory Account           Dr (BALANCE SHEET)

To COGM Account                Cr (PROFIT & LOSS ACCOUNT)

 

  1. Delivery to customer:

                   In-Transit Account             Dr. (BALANCE SHEET)

To FG Inventory Account     Cr (BALANCE SHEET)

 

  1. Invoicing to customer:

                   In FI:

Customer Account             Dr (BALANCE SHEET)

To Revenue Account          Cr (PROFIT & LOSS ACCOUNT)

 

COGS Account                  Dr (PROFIT & LOSS ACCOUNT)

To In-Transit Account       Cr (BALANCE SHEET)
 
In CO: COGS and Revenue are posted to COPA Period end closing – Production Order
 
  1. Revaluation of activity prices: Production Order and Cost Center will be debited or credited as the case may be
  2. Calculation of WIP In FI:

      WIP Account                           Dr. (BALANCE SHEET)

To Change in WIP Account      Cr (PROFIT & LOSS ACCOUNT)

 

If the Order is completed:

 

In FI:

 

Change in WIP Account           Dr (PROFIT & LOSS ACCOUNT)

To WIP Account                     Cr (BALANCE SHEET)

 

  1. Calculation of Variances: Variances are calculated on the Production Order. No FI or CO entries
  2. Settlement to Sale Order: Production Order and Sales Order will get debited/credited depending on whether they are positive or negative variances.  
  3. Result analysis at Sale Order: Result Analysis run will identify the status of the sale order and will enable the postings to COPA at the time of settlement
  4. Settlement of Sale Order:

In FI:

 

Variances Account                        Dr (PROFIT & LOSS ACCOUNT)

To COGS Account                         Cr (PROFIT & LOSS ACCOUNT)

(It would be otherwise if variances are positive)

 

In CO:

 

COGS, Revenue and Variances are settled to COPA

  

SAP Scenario 2 – Non-valuated Sale Order Stock – with Sale Order Controlling: Process Step Business Process Flow Value Flow – FI/CO

 

  1. Enquiry
  2. Opportunity
  3. Quotation (Creation and Approval)
  4. Creation of Sale Order
  5. MRP Run – Creation of Planned Order – Creation of Production Order and Purchase Order
  6. External Procurement – Goods Receipt

 In FI:

 

Consumption Account             Dr (PROFIT & LOSS ACCOUNT)

To GR/IR Account                  Cr (PROFIT & LOSS ACCOUNT)

 

In CO: Material costs will directly get posted to Sale Order

 

  1. Material Consumption to Production Order:             -           Not applicable
  2. Activity Consumption to Production Order

In FI: No Entry

In CO: Activity Costs are posted to Production Order

 

  1. Goods Receipt from Production Order:
    1. Only Material Document for movement of goods will be there.
    2. The stock is neither valuated in CO nor in FI
  2. Delivery to customer:
    1. Just goods movement from sale order stock to customer.
    2. No value postings in FI and CO
  3. Invoicing to customer

 In FI:

 

Customer Account                 Dr (BALANCE SHEET)

To Revenue Account             Cr (PROFIT & LOSS ACCOUNT)

 

In CO: COGS and Revenue get posted to Sale Order Period end closing – Production Order

 

  1. Revaluation of activity prices: Production Order and Cost Center will be debited or credited as the case may be
  2. Calculation of WIP:                 -           No WIP
  3. Calculation of Variances:            -           No Variances
  4. Settlement of costs to Sale Order: All the costs accumulated in Production Order gets collected to Sale Order
  5. Settlement of Variances: No Variances in Production
  6. Result analysis at Sale Order:

In FI:

 

WIP Account                                Dr. (BALANCE SHEET)

To Change in WIP Account            Cr (PROFIT & LOSS ACCOUNT)

 

If the Order is completed:

 

Change in WIP Account               Dr (PROFIT & LOSS ACCOUNT)

To WIP Account                         Cr (BALANCE SHEET)

 

No CO postings will happen

18.   Settlement of Sale Order: COGS, Revenue and other direct sale order related values will get posed to PA.

 

 

 

Co-Product Configuration (for Cost Estimate)

Co-Product Configuration for following scenario:

 

Product A (Parent Material / Input Material), Product B, C and D are child materials (output materials). During manufacturing of Product B, we get 40% of Product D and the remaining 60% will be product B. Product is C is not the co-product, it always gets produced for 100%.

 

Solution:

 

Product B is the one you are trying to manufacture in the production process. And while doing so, the input material is A and Product D is produced. In this process Product C always gets produced.

 

B & D are co-products. C is the by-product according to the definition of these by SAP. And A is the input material. Please create the BOM for B in which A will be having a +ve qty and C & D will have -ve qty.

 

First, you have to create the BOM for B instead of A, since B is the one getting manufactured and not A. A will be either procured or manufactured in a different process. You will define BOM for A only for the process, which manufactures A.

 

We have to check Co-product indicator in Material Master (MRP2 View) for Product B and D.

 

Product B and D should have co-product checked in their "Basic Data" tab of BOM View (BOM view of Product A, I mean). For C you will have to tick the check box Fixed Price Co-Product in the Material Master Costing 1 view.

 

We have to have Apportionment structure in MRP2 View (Joint Production Button) for Product B only, and that apportionment structure (assuming we don't use Source Structure) with equivalence number will have 2 products - product B with equ. number = 60 and Product D with eq. no = 40).

Document Number not in sequence ...

Issue:
 
Gaps (jumps) occur when allocating internal numbers.
The status of the number range interval does not match the number that was last assigned.
The number assignment does not reflect the insert sequence.
 
Applicable for below TCODES:
 
FB01, VF01, KO88, KE21, KE11, FD01, FK01, XK01, XDN1, MB01, MB0A, MB11, MB1A, MB1B, MB1C, MB31, KANK, KB11, KB13, KB14, KB41, KB43, KB44, KB21, KB23, KB24, KB31, KB33, KB34, KB51, KB53, KB54, PR01, PR02, PR03, PR04, PR05, XD01, VD01, MK01, SNUM, SM56, SNRO, VL01, VL02, CO01, CO40, CO41, VA01, MR1M, MIRO.
 

Reason:

 

A large number of number range objects are buffered. When the system buffers a number range object, it does not update numbers individually in the database but reserves a preset group of numbers in the database the first time a number is requested, and makes these numbers available to the application server in question. The following numbers can then be taken directly from the application server buffer. New numbers are not used in the database until the application server buffer has been used up.

 

Buffering the number range objects has a positive effect on performance, because the system no longer has to access the database (number range table NRIV) for each posting. Furthermore, a serialization of this table (database locking) is prevented to a large extent so that posting procedures can be carried out in parallel.

 

Solution:

 

Since number range buffering does not cause any expressly assured qualities to be lost, no correction is required.

 

If you still require continuous allocation, you can deactivate the number range buffering specifically for individual objects.

 

Proceed as follows:

 

  1. Start Transaction SNRO and enter the affected object.

 

  1. Choose 'Change'.
  2. Deactivate buffering: Choose 'Edit' -> 'Set Up Buffering' -> 'No Buffering'.
  3. If you want to change the buffer size only, enter the corresponding value in the field 'No. of numbers in buffer'.
  4. Save the changes.

 

Number range buffering can be activated or deactivated at any time.

Number range objects that have to be continuous due to legal.

 

For the following number range objects, gaps may cause:

 

Area CO:

 

- RK_BELEG   (CO Document)

CAUTION: Note that the problems described in Notes 20965 and 29030 may occur if you deactivate buffering.

- COPA_IST (Document number in actual posting)

- COPA_PLAN  (Document number in planned posting)

- COPA_OBJ   (Profitability segment number)

 

Area FI:

 

- DEBITOR    (Customer master data)

- KREDITOR   (Vendor master data)

 

Area HR:

 

- RP_REINR  (Trip numbers)

 

Area PM, PP, PS

 

- AUFTRAG    (Order number, production, process, maintenance order, network number)

- QMEL_NR    (Number range - message)

 

Area MM:

 

- MATBELEG   (Material documents)

- MATERIALNR (Material master)

 

Area QM:

 

- QLOSE      (Inspection lots in QM)

- QMEL_NR    (Number range - message)

- QMERK      (Confirmation number)

- QMERKMALE  (Master inspection characteristics in QSS)

- QMERKRUECK (Confirmation number of an inspection characteristic in QM results processing)

- QMETHODEN  (Inspection methods in QM)

- ROUTING_Q  (Number ranges for inspection plans)

- QCONTROLCH (Quality control chart)

 

Area Workflow:

 

- EDIDOC     (IDocs)

 

 

For other possible solutions, refer to the following notes: 37844, 23835, 179224, 678501, 599157 and 840901.

 
IMPORTANT: Read Notes 504875 and 678501.

What type of qustions need to ask to client before sap fico prject start ?

Initially you need to prepare topics wise questions and in the process the data collection should be from 2 sources i.e. Primary - collecting information directly by interacting with the client and the other one is Secondary - from the documents that you collect from the client.

 

After formal introduction during the Kick off meeting never directly jump down to interact with the client you need to patiently observe the day-to-day business process of the client - department wise for the first few days. Do document all the observations that are made by you, this will help you to analyze the gap between the legacy system and standard SAP Process.

 

The first and the foremost thing is that we need to see on what platform all the business process relating to Accounting is maintained i.e. the software used to store the legacy data.

 

Now I will mention some of the important points that can be used a checklist during your interaction with the client.

 

           1.We are the consultants who need to freeze the Enterprise Structure first and later on the other module consultants will add their respective enterprise elements to the enterprise structure freezed by us. Therefore this process will by itself will take not less than 1 to 2 months. This process is the typical phase where a lot of interaction/understanding/experience will come into limelight. So be attentive and observe the process thoroughly, once the Enterprise Structure is freezed and configured we cannot withdraw from the system.

 

           2. Codification of the Enterprise Elements play a vital role does follow some naming convention. Here coding can be in 3 forms i.e. pure numeric, alphanumeric or pure alphabets.

 

           3. Identify the chart of accounts that is maintained.

 

           4. Grouping process of the GL Account According to Schedule VI of Companies Act 1956

 

           5. Customer & Vendor Grouping - payment terms maintained - Down payment if applicable - how the memos maintained.

 

           6. Collect all the documents relating to Procurement Process right from indent preparation to billing and followed by payment. This is very useful.

 

           7. CIN plays a very important role regarding this we will have a separate session in the days to come.

 

This is just a beginning and hope this will help you and as the time comes up do feel free to put up questions at cavenco@gmail.com and I will clarify for the same.

Step by Step Credit Management Configuration : SAP : Check List

  1. Transaction OB38 Check which credit control area is assigned to the company code.
  2. Transaction OVFL Check which credit control area is assigned to the sales area.
  3. Transaction XD02 or VD02 Check which credit control area is assigned to the payer.
  4. Transaction SE37 Is user exit EXIT_SAPFV45K_001 being used?
  5. Transaction OBZK For the settings under items 2 - 4, field "All company codes" must be marked in Transaction OB45, or the credit control area must be entered under the relevant company code in table T001CM of the credit control areas allowed. 
  6. Settings for the credit checks : 
    • Transaction OVAK which settings do exist for the sales document type used?
    • Transaction OVAD Which settings do exist for the delivery type used?
    • Transaction OB01 Credit management/Change risk category Definition of the risk category for each credit control area. You can use Transaction FD32 to assign this risk category to a credit account.
    • Transaction OVA8 Here, the individual credit checks for key fields - credit control area - risk category - credit group are set. Take these key fields from the above settings and go to the detail screen. In particular, check whether fields "Reaction" and "Status/block" are set correctly. To carry out follow-up actions in case of a credit block, the credit check status must be set (field "Status/block").
    • Transaction FD32 Credit master data for the payer of the relevant document.
    • Settings for updating the credit values Update of the credit values is required for the limit check (static or dynamic credit limit check).
    • You want the item to be relevant for billing. If an item is not relevant for billing or for pro forma billing, no update occurs.
    • Transaction OVA7 Update of the credit value is active for the corresponding item type if the check box is marked. This field corresponds to field "Active receivable" in Transaction VOV7.
    • Transaction V/08, Pricing In the pricing procedure used for pricing, subtotal "A" must be entered in a line for determining the credit value (mark the pricing procedure and doubleclick on "Control"). Usually, the net value plus taxes is used. This way the system is determined to use this subtotal for credit pricing. The credit price is stored in field VBAP-CMPRE and used for update and credit check. You can find the used pricing procedure of the order under "Item -> Condition -> Analysis". Pricing procedure: Line with subtotal = 'A':
    • Transaction OB45 Which update group (field "Update") do you use in the relevant credit control area? The default setting is "12". If you use another update group, check whether this is fine with you. If you open an OSS message, please tell us the alternative update group.
    • Transaction OMO1 Which kind of update did you choose for structure S066? In any case, "Synchronous update (1)" has to be chosen as the kind of update. All other settings will lead to errors.

Configuration for Provident Fund

There is no special configuration for PF.

You should know the entries you are going to post for PF.

You can either post manually or upload through GL program (to be developed).

You need to create the employee as a Vendor using seperate account group with external number range.

You need to post with a noted item special GL indictor where you can keep the PF balance for each employee.

Functionality of the Electronic Bank Statement

1.      There are different programs to upload electronic bank statement. FF.5 or FF_5.

2.      In case, if you are using Multicash format. You need to have three files in FF.5 and two files in FF_5

3.      You can prepare a Z program in order to truncate the electronic bank statement into two or three part files and save them on the application server.

a.      Take all the external codes list from bank.

b.      Take any available documentation from the Bank describing the relevance of the external codes.

c.       Make sure that your Chart of Accounts (Bank Accounts) last digits logic is appropriate to meet the requirements.

d.      Based on this decide the Account Symbols that are required to be created.

e.      Make sure that the masking rules are configured properly.

f.       Decide the posting rules that needs to be created.

g.      Link up your external symbols provided by the bank with Posting rules and give proper algorithms for posting and clearing logic.

h.      Concentrate on the posting areas to be posted while uploading the bank statement.

 

Further explanation would help you to understand the functionality when uploaded the electronic bank statement.

 

1.      Main purpose of uploading the bank statement into SAP is to make your Bank Main Account and physical bank statement balance in sync.

2.      You do not have any traditional Bank Reconciliation Statement (BRS) report in SAP.

3.       In SAP normally you maintain bank main account and bank sub account.

4.      Whenever you make a payment through F-53 or F-58 or F110, the entry would be:

Vendor Account Dr

To Bank Sub Account

5.      The ending digits of the sub-account would be important in configuring the masking rule. Based on this masking rule when you upload the bank statement the entry the system would pass the below journal entry:

Bank Sub Account Dr

To Bank Main Account

6.      It depends on the configuration, either the sub account will be cleared by the system automatically or you need to run F.13 to clear the sub accounts.

7.      At the time of receipts, you have different accounting entries unlike payments.

8.      It needs to post to two posting areas.

a.      GL Accounting

b.      Sub-Ledger Accounting

9.      The entries would system itself pass is:

Bank Main Account Dr

To Bank Sub Account

 

Bank Sub Account Dr

To Customer account.

 

10.   Clearing logic mentioned for your posting rules and the algorithm used for your external bank symbols will also play pivotal role in clearing the accounts.

11.   Ideally you will use FF67 / FF.5 / FF_5 for uploading manual or electronic bank statement FEBA / FEBA_BANK_STATEMENT is used for further processing.

12.   GO THROUGH SAP NOTE 48854 Please go through SAP Note. 48854. You will get an idea regarding the functionality of the algorithms. Though this note is in relevant to GB specific, you will find this very useful.

13.   Description follows below regarding the normal procedure for maintaining table T028G. Due to the different bank codes and posting rules, pre-Customizing is not possible at this point.

14.   The following processing types are available - unless stated otherwise, you should use the interpretation algorithm: '000 - No interpretation' in each case. 

a.      '00': There is no processing. The entry line is ignored.

b.      '01': A validation is made whether an entry exists for the transferred check number in the check table (PAYR). The check number and payment document number are transferred for further processing. Interpretation algorithm: outgoing check processing '011'-'013'; the update in the check file is via the interpretation algorithm.

c.       02': Transfer of the ending balance to the electronic bank statement

d.      '03': Transfer of the opening balance to the electronic bank statement

e.      '04': Clearing via the allocation number which is delivered with the bank statement. No interpretation algorithm.

f.       '05': Clearing of BACS payments or BACS bank collection. The reference text field is first read to ascertain whether it involves payments initiated by users or bank collection via BACS. Providing it does involve a cash transaction initiated by the user, the payment document numbers concerned are determined via the reference number and transferred as a reference to further processing. Interpretation algorithm: '000 - No interpretation' or '019 - Reference number DME'. Note To differentiate between the two procedures in table T028G, you have to maintain two separate entries. Example: the bank uses bank code '62' for cash receipts and for BACS bank collection. Ext. Transaction +/- sign Posting rule Int. Algorithm Processing type 62 + GB62 001 5 62 SAPBACS + GB63 000 5

g.      '06': Bank costs or interest revenues Recommended interpretation algorithm: '000 - No interpretation'

h.      '07': Total amount of cash disbursements

i.        '08': Total amount of cash receipts

j.       '09': Items not paid Recommended interpretation algorithm: '000 - No interpretation'