KK~SAP

FI-MM: The integration between FI-MM happens in T-code OBYC. 

  1. When PO is created :

       ---- No Entry -----

  2. When GR is posted 

      Inventory Account dr (Transaction Key BSX in OBYC)
            To GRIR account (T.Key WRX in T-code OBYC)

  3. When Invoice is posted

      GRIR account Dr.
      Vendor account  Cr.

  4. Payment made to Vendor

      Vendor A/c Dr
            To Bank Clearing A/c Cr.

Points to know : Movement Types, Assignment of Movement types to T-keys (T-code OMJJ), Value string (I also need some information on this) , OMWN and OMWB transactions. 

---

There is a close integration b/w FI & MM, actually document flows from MM to FI in the following areas such as,
   
 1. Movement Types:
 
Used to enable the system to find the predefined posting rules determining how the accounts of financial accounting system are to be posted & to update the stock fields in the matrl master data.(Goods Receipt, Goods Issue, etc)
   
 2. Valuation Class:
   
Assignment of material to grp of gl account, used to determine the gl accounts that are updated as a result of goods movement.
   
 3. Transaction/Event key:
   
Used to control the storage or filing of documents & assignment of documents.Used to differeniate b/w various transactions such as goods movement tht occur in inventory.
   
 4. Material Type:
   
Each material should assign mtrl type in mtrl master record used to update whether changes made in qty are updated in material master record & change in value also updated in stock account.
   
 FI-SD Integration: The integration is done in T-code VKOA

  1. Sales Order Created 

        ---No Entry---

  2. PGI done (Goods issue)

      Cost of Goods Sold     Dr (Configured in OBYC GBB T-Key)
           To Inventory Account

  3. Billing document released to Accounting

        Customer Account Dr.
              To Sales Revenue Account (ERL T-key in Pricing procedure)

  Note : The GL account is assigned to this ERL in VKOA

  4. Payment Received

        Bank Clearing A/c Dr
                       Customer A/c Cr. 

Points to Know : Good to understand the pricing procedure and how the different transaction keys are used like ERL, ERS etc.

Trackback: http://tb.blog.csdn.net/TrackBack.aspx?PostId=1777695

Define Pricing Procedure

• Select the pricing procedure which is the standard and copy it and create our own pricing procedure.
• Highlight it and double click the Control icon in the LHS screen.
• We can see that there are 16 columns in the pricing procedure, these are going to be used by the system to control the condition types.
• The detail description of each column is given below.

Step:

• Number that determines the sequence of theconditionswithin a procedure.
• It indicates the position of the condition type in pricing procedure.
• Ex.: 10, 15 etc.

Counter:

• System uses the counter to count the steps and also it can be used to count mini steps of same condition types. So that number of steps can be reduced in the pricing procedure and hence enhancing the system performance.
• Access number of the conditionswithin a step in the pricing procedure.
• During automatic pricing, the system takes into account the sequence specified by the counter.

Condition Type:

• It represents pricing element in pricing procedure as a base price, discount, freight and tax.
• The condition type is used for different functions. In pricing, for example, the condition type lets you differentiate between different kinds of discount; in output determination, between different output types such as order confirmation or delivery note; in batch determination, between different strategy types.
• Ex.: PR00 - Price

K004 - Material Discount

K005 - Customer/Material Discount

K007 - Customer Discount.

Description:

• System copies description of condition type from its description (V/06).

From and To:

1. From:This can be used as a base to the condition type for calculating further value.

1. {+}From and To:+ The range between the steps from and to can be used to specify the range between same condition types. So that depending upon the condition type, the system deducts or adds the total value of those condition types from specific common source.

Manual:

• This indicator specifies whether the specific condition type can be determined manually during sales order processing.
• If we check the box then the entry is going to be manual, if we uncheck it, it is going to be automatic.
• For Base Price and Taxes, the entry should be automatic.
• For Discounts and Freights, The entry should be manual.
• If we check the box, in VA01 when we go to conditions at the header/item level, the condition type will not be listed. If we require we will have to manually enter it.
• If we uncheck the box, in VA01 when we go to conditions at the header/item level, the condition type will be listed.

Mandatory:

• This indicator specifies that particular condition type is mandatory in the pricing procedure.
• If we check the box, then in VA01 at the header/item level in the conditions tab, if we delete the value in the condition type and try to save the document then system will not allow us to do it and throws an error.
• If we uncheck the box, then in VA01 at the header/item level in the conditions tab, if we delete the value in the condition type and try to save the document then system will allow us to save it, without giving any error.
• Mandatory check box should be checked in condition types which are compulsorily required in pricing procedure. Ex.: PR00, MWST.
• If the condition type is checked with mandatory option, then value should be maintained for that condition type, otherwise the system will not allow the user to process the document.

Statistical:

• This indicator if it is activated will not allow the value of the condition type to be taken into net value calculation.
• It is used only for information purposes only.
• This indicator causes a surcharge or discount to be set in the document statistically (that is, without altering the value).
• This is commonly used for condition types
  • SKTO - Cash Discount
  • VPRS - Cost (Moving average price/Standard Price).

Print:

• The value of this field specifies whether line item can be printed or not in the sales document and at what level it is to be printed.

Subtotal:

• The value of this field determines where the values of subtotals to be captured i.e. in which table and which field.
• Controls whether and in which fields condition amounts or subtotals (for example, a customer discount or the cost of a material) are stored.
• If the same fields are used to store different condition amounts, the system totals the individual amounts.
• These condition amounts or subtotals are used as a starting point for further calculations. You may, for example, want a subtotal of all the discounts included in the pricing of a sales order.

Requirement:

• It is a routine that is written by an ABAP consultant according to the business requirement.
• By defining Requirement in condition technique we can restrict the access of condition type.
• To understand the concept, we will take the example of the Rebates. Rebates are to be included during the billing document processing and not in the sales document processing. As rebates are given on the delivered quantity and not on the ordered quantity (in case of cut-off period for rebates).
• For rebates we use the condition types BO01 to BO05, and in the Requirement column we give the value 24 which is "Only in Billing Document".
• This Requirement will ensure that these condition types will appear only during the billing document processing.
• If new Requirements are to be defined we follow the procedure given below.
  • Go to T.Code: VOFM. - Maintain Requirements & Formulas
  • Click on the "Requirements" in the top menu and then click on "pricing".
  • We have a list of requirements, we can ask ABAP consultant to create new requirement based on the client requests.
  • And we assign the application type like V - Sales/Distribution etc.

AltCty - Condition formula for alternative calculation type:

• It is again a Routine that is written by ABAP Consultant.
• It is an alternative formula for the condition type that can be used instead of standard formulas.
• For example, let us take the Profit Margin which can be both + / - , so here this routine will help us in generating the value which can be either + or -. Profit margin is not a condition type so it cannot be classified as +ve or -ve in the V/06.
• Ex.: 950 0 Profit Margin 11.
• So we assign 11 - Profit Margin.
• If new routines are to be defined we follow the procedure given below.
  • Go to T.Code: VOFM. - Maintain Requirements & Formulas

• • Click on the "Formulas" and then on the "Condition Values".
  • We have a list of routines, we can ask ABAP consultant to create new routines based on the client requests.
  • And we assign the application type.

AltCBV - Alternative formula for condition base value:

• Formula for determining the condition basis as an alternative to the standard.
• It is again a Routine that is written by ABAP Consultant.
• It is used as a basis to calculate value of the condition type instead of using it from the "FROM" column.
• Ex.: Freight - KF00.
• Freight is calculated based on weight, volume etc. and not on the base price. In pricing there is no entry of weight from which the value can be referred like we do for discounts using base price. We have to get the value from the Material master.
• In this column we can mention the value as 12 - Gross Weight or 13 - Net Weight.
• During pricing, the system will consider the value that is mentioned in this column and determine the freight based on this value.
• Suppose we have Net weight: 100 kgs and Gross Weight: 150 kgs. And if we mention 13 in this column then the Freight condition KF00 will be calculated using the weight as 100 kgs.

AcyKy - Account Key/ Accrls - Accruals:

• The values of the Sales Revenues, Sales Deductions, Freight Revenues, Tax Revenues, and Rebate Accruals etc. are going to be posted in the respective G/L accounts in Fi Module.
• In order to do this we assign account keys/ accruals to the different condition types based on their classification. The classification shown below.
  • ERB Rebate sales deduct.
  • ERF Freight revenue
  • ERL Revenue
  • ERS Sales deductions
  • ERU Rebate accruals
• For Ex.,
  • For all Price condition types like PR00 etc. we assign ERL - Revenue.
  • For all Discount condition types like K004, K005 etc. we assign ERS - Sales Deductions.
  • For all Freight condition types KF00 etc. we assign ERF - Freight Revenues.
  • For all Rebates condition types BO01 to BO05 we assign in Account key ERB - Rebates Sales deductions and for Accruals ERU - Rebate Accruals.
• This account keys and accruals are in turn assigned to respective G/L accounts. So the system posts respective values in respective G/L accounts in Fi-Co Module.
• This also one of the areas of SD - Fi Integration. SD consultants assign the account keys and Fi Consultants assign the respective G/L accounts in T.Code:VKOA.

有时候需要暂时锁定客户的往来业务，你可以使用下面的TCODE

VD05 - Block/Unblock Customer

OVAS - Sales Order Type Blocking reasons
OVAL - Blocking reasons links with Sales Order Type

OVZ7 - Delivery Blocking reasons
OVV3 - Billing Blocking reasons

SM30 - Table/View   V_TVFSP

*&---------------------------------------------------------------------*
*& Report  ZZWASTOR                                                    *
*&                                                                     *
*&---------------------------------------------------------------------*
*&                                                                     *
*&                                                                     *
*&---------------------------------------------------------------------*
REPORT ZZWASTOR .

*********************************************************************
* If you do not know the material document of the goods issue any   *
* more you can use transaction SE16.                                *
* - Type in table name MKPF                                         *
* - Type in the delivery note number in field XBLNR (always with    *
*   leading zeroes)                                                 *
* - Execute                                                         *
* - The Material document number of the goods issue for the deleted *
*   delivery will be shown.                                         *
*                                                                   *
*                                                                   *
*                                                                   *
* LF_BUDAT  =>  Posting date for the reversal                       *
* LF_MJAHR  =>  Posting year of the material document to reverse    *
* LF_MBLNR  =>  Goods issue document (with leading zeroes)          *
* LF_VBELN  =>  Delivery note number (with leading zeroes)          *
* LF_TEST   =>  When 'X' it is test mode only, otherwise GI will be *
*               cancelled                                           *
*********************************************************************

TABLES: MKPF, IMKPF, EMKPF, LIKP.

DATA:   BEGIN OF IMSEG OCCURS 0.
        INCLUDE STRUCTURE IMSEG.
DATA:   END OF IMSEG.

DATA:   BEGIN OF EMSEG OCCURS 0.
        INCLUDE STRUCTURE EMSEG.
DATA:   END OF EMSEG.

PARAMETERS: LF_BUDAT  LIKE SY-DATLO DEFAULT SY-DATLO OBLIGATORY,
            LF_MJAHR  LIKE MKPF-MJAHR DEFAULT SY-DATLO(4) OBLIGATORY,
            LF_MBLNR  LIKE MKPF-MBLNR OBLIGATORY,
            LF_VBELN  LIKE LIKP-VBELN OBLIGATORY,
            LF_TEST   TYPE C DEFAULT 'X'.

DATA:   MBLPO LIKE MSEG-ZEILE.

SELECT SINGLE * FROM MKPF WHERE MBLNR = LF_MBLNR
                          AND   MJAHR = LF_MJAHR
                          AND   XBLNR = LF_VBELN.

IF SY-SUBRC IS INITIAL.
  CALL FUNCTION 'MB_CANCEL_GOODS_MOVEMENT'
    EXPORTING
      BUDAT     = LF_BUDAT
      MBLNR     = LF_MBLNR
      MBLPO     = MBLPO
      MJAHR     = LF_MJAHR
      TCODE     = 'VL09'
      CALLED_BY = 'VL09'
    IMPORTING
      EMKPF     = EMKPF
    TABLES
      EMSEG     = EMSEG
      IMSEG     = IMSEG
    EXCEPTIONS
      OTHERS    = 1.

*... No error found, then it will be posted
  IF EMKPF-SUBRC EQ 1.
    IF LF_TEST IS INITIAL.
      CALL FUNCTION 'MB_POST_GOODS_MOVEMENT'
        EXPORTING
          XBLNR_SD = LF_VBELN
        IMPORTING
          EMKPF    = EMKPF
        EXCEPTIONS
          OTHERS   = 0.

      COMMIT WORK.
    WRITE: / 'Goods movement was cancelled successfully with document:',
            EMKPF-MBLNR.
    ELSE.
      WRITE: / 'Testmode: Goods movement could be cancelled !'.
    ENDIF.
  ELSE.
*... otherwise write an error-log
    LOOP AT EMSEG.
      WRITE: /
                EMSEG-MSGID,
                EMSEG-MSGNO,
                EMSEG-MSGTY,
                EMSEG-MSGV1,
               EMSEG-MSGV2,
               EMSEG-MSGV3,
               EMSEG-MSGV4.
    ENDLOOP.
    WRITE: / EMKPF-MSGID,
             EMKPF-MSGNO,
             EMKPF-MSGTY,
             EMKPF-MSGV1,
             EMKPF-MSGV2,
             EMKPF-MSGV3,
             EMKPF-MSGV4.

  ENDIF.
ELSE.
  WRITE: / 'Material document to reverse does not exsist'.
ENDIF.
                                              .
 

Trackback: http://tb.blog.csdn.net/TrackBack.aspx?PostId=1806383