F.05 Revaluation issue

Hi
I believe, when we reun F.05 we give posting date and reversal date. We also tick in create posting and reversal posting check boxes. Once done, when we execute F.05 , system should post valuation difference and then reverse the same on the reversal date.
In my case, reversal is not happening inspite of giving reversal date and ticked in the reversal postings. Hence when I go to clear the original document, system is generating additional line item for balance sheet item which got posted during F.05 valuation.
Please suggest
For better understanding
FB60 entered for foreign currency and the F.05 executed
Posting date given as 08/31/2008 and the reversal date is given as 09/01/2008.
System is creating entry for 08/31/2008 but reversal entry dd not get created
Raj

Hi,
The check box 'Bal Sheet Preparation Valun' and the check box for reversing entry are mutually exclusive.
With Balance Sheet Valuation, the system will change all open items and record in each document a valuation difference. This way, in the following month, when you do the same, the system will only record the Difference between last month's value and this month's value. For this reason, the system will not allow you to reverse this entry.
If you don't check the Balance Sheet Valuation box, then the system will force you to make a reversing entry (for open item managed accounts), and the revaluation at the end of the month will always be the difference between the current value and the historical value.
Hope this helps, best regards,
Pascal

Similar Messages

  • Asset Revaluation issue - Reval of Current year depreciation

    Hi All,
    We are setting up the system to do asset revaluation for our company code in South America. My client wants to
    revalue the assets from Jul'09 to Dec'09.
    1) We have maintained inflation indexes for the last day of each period in the year 2009.
    2) Maintained Posting Variants and Time Base and Exposure variant accordingly for all the periods and year as 9999.
    3) Assigned the appropriate Time base and exposure variant in the period control method.
    4) Maintained the Revaluation Areas:
    a) Area 01 - Book
    b) Area 02 - Inflation Adj (Revaluation Area)
    c) Area 03 - Derived (Area 01+Area02)
    d) Area 22 - Infla Adj in Group Currency
    5) Maintained the Revaluation key and assigned it to the relevant Asset classes by Depreciation Area (02 and 22)
    6) Maintained the transaction types as below:
    897 - Revaluation (downward) current year
    892 - Revaluation (upward) current year
    891 - Revaluation (downward) prior year
    893 - Revaluation (upward) prior year
    7) Maintained the Inflation Method and last revaluation date on Inflation method as 01.07.2009.
    8) We have also activated the Revaluation after useful life.
    With this setup in the system I took a test asset which had depreciation postings for the period 08 and 09. When I
    ran the J1AI - Revaluation (Inflation) Program in the test run mode the outcome was that the APC value of the asset
    was being revalued and Revaluation of Prior year Depreciation but not the Revaluation of current year
    Depreciation. Can anyone tell me why current year Depreciation is not being revalued.
    Am I doing something wrong process-wise or configuration-wise?
    Please help me in resolving this issue.
    Regards,
    Raj

    Hi Rajesh Phanibatla,
    I've always happened that Issue. But what I realized is that although the program output (J1AI) does not show you nothing on "Rev of CY Depn", the system calculates. This only happens for the first month of adjustment (In your case, Aug 08).
    Try checking the test asset with the Assets Explorer (AW01N) just after running the adjust (J1AI) in background process (NO test mode) at 31.08.2009. See if the area Area 02 - Inflation Adj (Revaluation Area) on "Posted values" tab shows something different to zero on month 08 with "Planned" status.
    Then, for the adjustment of the following months, the output of the program will show you the "Rev of CY Depn" value.
    If you want, let me know your email to show you a presentation (PowerPoint in spanish) that has screens that I captured on that occasion that happened to me.
    I hope this is your case and can help you that I said.
    Good Look!
    PD: Sorry for my bad english :S

  • 11i General Ledger : Translation and Revaluation issue.

    Hi,
    I'll post the problem as descriptively as i can.
    * The client has an Equity account under the natural code of 7341. He has not defined the GL : Owner's Equity Translation rule.
    * The currency rate table shows that the rate type used for this natural code is Period
    * Functional currency is USD
    In August 2006, the client had made an entry to this account to the value of AUD 24,713 which was converted at journal entry point to USD 18,977. The entry was subsequently reversed in September 2008 and the USD book shows a '0' balance after it, which is correct. Just before the reversal the balance was USD 21,332 (taking into account subsequent revaluations till Aug 2008)
    Client performs monthly translations and revaluations. In August 2006, the entry was translated to LKR books with a value of LKR 1,929,634. After which monthly revaluations which happened in the functional currency books also got translated and hit the LKR books till September 2008.
    The total USD reversal in USD books as stated earlier was USD 21,332. This comprised of an initial entry and subsequent revaluations that were translated LKR books at different historical rates. But the reversal was translated to LKR books only on the closing rate as at September 2008. Leaving a small LKR balance of just over 100k.
    Is there anyway that the client can perform the translation in such a way that after the reversal the closing value of the LKR books is also '0'. Please note that he is not willing to change the classification of the account from Owner's Equity.
    Thanks,
    Miranga

    Instead of reversing the Original Journal, Pass a reversal entry nullifying the effect of the Original Entry.
    Hope it resolves your issue.
    Regards,
    Sridhar

  • Revaluation Issue

    Hi MM Gurus,
    Is there any way we can revaluate based on a GR 101 material document?
    I want to revluate a single GR on a PO line item where multiple GR exists.
    Please advise.
    Regards,
    Senthil

    a revaluation of your stock can be made with MR21 and MR22 transaction.
    a single receipt cannot really be revaluated. you can cancel the GR, then change the PO price and receive it again. (but cancellations may even be different valuated than the original receipt, be carefull and test your scenario)

  • F.05 - Revaluation posting are not clearing in GL Account (Gr/Ir)

    Hi Gurus,
    We have FX revaluation issue. After execution of F.05 - the system performs an automatic reversal of the postings for the GRIR account on the first posting date of the new month but there is no valuation posting last posting date (month end).
    So, FX revaluation is not clearing in GL Account.
    Only one document posted for the first posting date of the new month and there is no posting for the month end valuation.
    Please advice, on how to clear the FX entries that are currently sitting as open item in GL (Gr/IR).
    Thanks

    Hi Tejas,
    Thank you for your reply. I have tried selecting various exchange rate type and was bale to post both valuation doc (for month end date) and reversal doc (for beginning of the date of next month).  In F.05 posting tab tab I couldn't find "Determine Automatically" filed. So not able to find what caused for these postings. This has been done for last 4 months and now there are open items setting in GL(Gr/Ir) which needs to be cleared.
    One more thing I am hearing from user is that when they run f.05 the posting cleared automatically. When I tried myself it doesn't clear the line items but post the tow line items with debit and credit. Is something  I am missing here.
    Please advise me on clearing the difference balances.
    Thanks

  • RMB/CNY currency

    Hi
    The official currency in China is the Renminbi - RMB or CNY, it's the same.
    Why do I have these two codes in the SAP? Can I delete one?
    I dont want my users to use both codes for the next reasons:
    Exchange rates maintainace issue.
    End of month revaluation issue.
    Reporting (for example customer account display - FBL5n, can sub total by currency)...etc.
    Thanks
    Ofer

    DEAR Ofer Cohen
    Check this IMG setting:
    Sap netweaver -> general setting ->currencies ->check currencies code;
    where you can maintain and delete the currencies
    The 'CNY' Is the one which is consistent with international currency. better to adopt this one...
    br
    sophie

  • Issue while doing Incoming Payment & Foreign Currency Revaluation

    Hi,
    When i am doing Customer Incoming Payment, we are getting one more line item Foreign Currency Revaluation with Zero amount.
    Bank A/c - Debit
    Customer A/c - Credit
    Foreign Currency Revaluaiton A/c - Credit
    Why Foreign Currency Revaluation Accounting is coming into the Picture? How can i remove this from settings? Please advise me..
    Thanks
    KC

    Hi,
    Check Table T030H, whether for the customer reconciliation account the entry is maintained there.
    Secondly, you are getting this entry because, the customer line item that you are clearing is in a currency different from your local currency.
    Regards,
    SAPFICO

  • Issue with Posting Date in F.05 - Foreign Currency Revaluation

    Hi All,
    We have a problem with the US-GAAP Foreign currency revaluation run which we're doing every month.
    Although the posting date is entered correctly (for this month as 30.09.2011), the postings that are created have the posting date of 31.07.2011. But the reversal date is right (01.10.2011).
    Could you please explain why wrong date is appearing.
    Thanks IN Advance
    Regards,
    Payal Saxena

    Hi,
    Have you scheduled any batch job to carry out the Foreign Currency Valuation? If yes, then check the variant which has been created for the program. There the posting date might have been entered as 31.07.2011. Dynamic date calculation must be maintained for the posting date.
    Thanks,
    Aman

  • Issues installing 0IC_C03 dataflow in BW 7.0

    Hi experts,
    We are trying to install the dataflow for stocks infocube (0IC_C03) in BW (release 700 level 0015) from Business Content (release 703 level 0008) and we get the following error message when installing the transformation from Infosource 2LIS_03_BF_TR to the cube:
    Start Routine: Syntax error in routine
    We have checked the code in the start routine and we get the following error message:
    E:In PERFORM or CALL FUNCTION "ROUTINE_9998", the actual parameter
    "SOURCE_PACKAGE" is incompatible with the formal parameter
    "DATA_PACKAGE".
    Has anybody faced with this issue before?
    Any help will be really appreciated.
    Regards,
    David

    Hi,
    Pls add the following code in the start Routine.
    **************Added as per note 1052648****************************************
         InfoObject: 0RMA_XCC RMA Cross-Company Code Stock Transfer.
            RMA_XCC           TYPE /BI0/OIRMA_XCC,
         InfoObject: 0RMA_LNK RMA Stock Transfer Reference Item.
            RMA_LNK           TYPE /BI0/OIRMA_LNK,
         InfoObject: 0RMA_RFLG RMA Relevance Flag.
            RMA_RFLG           TYPE /BI0/OIRMA_RFLG,
         InfoObject: 0RTHFEES Stock Transfer Fees.
            RTHFEES           TYPE /BI0/OIRTHFEES,
    *******End Added as per note*****1052648*************************************
    After adding the above code no syntactical error in start routine activate the Transformation.
    The Problem is Solved.
    In my system Start routine code:
    PROGRAM trans_routine.
          CLASS routine DEFINITION
    CLASS lcl_transform DEFINITION.
      PUBLIC SECTION.
    Attributs
        DATA:
          p_check_master_data_exist
                TYPE RSODSOCHECKONLY READ-ONLY,
    *-    Instance for getting request runtime attributs;
        Available information: Refer to methods of
        interface 'if_rsbk_request_admintab_view'
          p_r_request
                TYPE REF TO if_rsbk_request_admintab_view READ-ONLY.
      PRIVATE SECTION.
        TYPE-POOLS: rsd, rstr.
      Rule specific types
        TYPES:
          BEGIN OF tys_SC_1,
         InfoObject: 0STORNO Reversal indicator.
            STORNO           TYPE /BI0/OISTORNO,
         InfoObject: 0RT_PROMO Promotion.
            RT_PROMO           TYPE /BI0/OIRT_PROMO,
         InfoObject: 0VAL_CLASS Valuation class.
            VAL_CLASS           TYPE /BI0/OIVAL_CLASS,
         InfoObject: 0DOC_DATE Document Date.
            DOC_DATE           TYPE /BI0/OIDOC_DATE,
         InfoObject: 0STOCKTYPE Stock type.
            STOCKTYPE           TYPE /BI0/OISTOCKTYPE,
         InfoObject: 0STOCKCAT Stock Categories.
            STOCKCAT           TYPE /BI0/OISTOCKCAT,
         InfoObject: 0PSTNG_DATE Posting date in the document.
            PSTNG_DATE           TYPE /BI0/OIPSTNG_DATE,
         InfoObject: 0COMP_CODE Company code.
            COMP_CODE           TYPE /BI0/OICOMP_CODE,
         InfoObject: 0BWAPPLNM Application component.
            BWAPPLNM           TYPE /BI0/OIBWAPPLNM,
         InfoObject: 0MOVETYPE Movement Type (Inventory Management).
            MOVETYPE           TYPE /BI0/OIMOVETYPE,
         InfoObject: 0STOCKRELEV BW: Relevance to Stock.
            STOCKRELEV           TYPE /BI0/OISTOCKRELEV,
         InfoObject: 0CPPVLC BW: Purchase Value in Local Currency.
            CPPVLC           TYPE /BI0/OICPPVLC,
         InfoObject: 0CPSVLC BW: Sales Value in Local Currency.
            CPSVLC           TYPE /BI0/OICPSVLC,
         InfoObject: 0CPSTLC BW: Sales Value in Local Currency.
            CPSTLC           TYPE /BI0/OICPSTLC,
         InfoObject: 0CPQUABU BW: Amount in base unit of measure.
            CPQUABU           TYPE /BI0/OICPQUABU,
         InfoObject: 0VAL_TYPE Valuation type.
            VAL_TYPE           TYPE /BI0/OIVAL_TYPE,
         InfoObject: 0PROCESSKEY BW: Transaction Key.
            PROCESSKEY           TYPE /BI0/OIPROCESSKEY,
         InfoObject: 0BATCH Batch number.
            BATCH           TYPE /BI0/OIBATCH,
         InfoObject: 0MATMREA Reason for Goods Movement.
            MATMREA           TYPE /BI0/OIMATMREA,
         InfoObject: 0BUS_AREA Business area.
            BUS_AREA           TYPE /BI0/OIBUS_AREA,
         InfoObject: 0COSTCENTER Cost Center.
            COSTCENTER           TYPE /BI0/OICOSTCENTER,
         InfoObject: 0SOLD_TO Sold-to party.
            SOLD_TO           TYPE /BI0/OISOLD_TO,
         InfoObject: 0WHSE_NUM Warehouse number / warehouse complex.
            WHSE_NUM           TYPE /BI0/OIWHSE_NUM,
         InfoObject: 0STOR_LOC Storage location.
            STOR_LOC           TYPE /BI0/OISTOR_LOC,
         InfoObject: 0STRGE_BIN Storage bin.
            STRGE_BIN           TYPE /BI0/OISTRGE_BIN,
         InfoObject: 0STRGE_TYPE Storage type.
            STRGE_TYPE           TYPE /BI0/OISTRGE_TYPE,
         InfoObject: 0VENDOR Vendor.
            VENDOR           TYPE /BI0/OIVENDOR,
         InfoObject: 0MATERIAL Material.
            MATERIAL           TYPE /BI0/OIMATERIAL,
         InfoObject: 0DOC_NUM BW: Document Number.
            DOC_NUM           TYPE /BI0/OIDOC_NUM,
         InfoObject: 0BASE_UOM Base Unit of Measure.
            BASE_UOM           TYPE /BI0/OIBASE_UOM,
         InfoObject: 0DOC_YEAR BW: Document Year.
            DOC_YEAR           TYPE /BI0/OIDOC_YEAR,
         InfoObject: 0PROFIT_CTR Profit Center.
            PROFIT_CTR           TYPE /BI0/OIPROFIT_CTR,
         InfoObject: 0DCINDIC Debit/credit indicator.
            DCINDIC           TYPE /BI0/OIDCINDIC,
         InfoObject: 0LOC_CURRCY Local currency.
            LOC_CURRCY           TYPE /BI0/OILOC_CURRCY,
         InfoObject: 0PLANT Plant.
            PLANT           TYPE /BI0/OIPLANT,
         InfoObject: 0FISCVARNT Fiscal year variant.
            FISCVARNT           TYPE /BI0/OIFISCVARNT,
         InfoObject: 0CPNOITEMS BW: Number of Activities.
            CPNOITEMS           TYPE /BI0/OICPNOITEMS,
         InfoObject: 0CO_AREA Controlling area.
            CO_AREA           TYPE /BI0/OICO_AREA,
         InfoObject: 0DOC_ITEM BW: Document Line Number.
            DOC_ITEM           TYPE /BI0/OIDOC_ITEM,
         InfoObject: 0VALUE_LC Amount in local currency.
            VALUE_LC           TYPE /BI0/OIVALUE_LC,
         InfoObject: 0COORDER Order number.
            COORDER           TYPE /BI0/OICOORDER,
         InfoObject: 0QUANT_B Quantity in base units of measure.
            QUANT_B           TYPE /BI0/OIQUANT_B,
         InfoObject: 0MOVE_PLANT Receiving Plant/Issuing Plant.
            MOVE_PLANT           TYPE /BI0/OIMOVE_PLANT,
         InfoObject: 0RECORDMODE BW Delta Process: Update Mode.
            RECORDMODE           TYPE RODMUPDMOD,
         InfoObject: 0BWCOUNTER Additional Key Field Revaluation Document
    *Record.
            BWCOUNTER           TYPE /BI0/OIBWCOUNTER,
         InfoObject: 0INDSPECSTK Indicator: Valuation of Special Stock.
            INDSPECSTK           TYPE /BI0/OIINDSPECSTK,
         InfoObject: 0GN_R3_SSY Source System for R/3 Entity.
            GN_R3_SSY           TYPE /BI0/OIGN_R3_SSY,
         InfoObject: 0RT_MOVINV Movement Type is Physical Inventory.
            RT_MOVINV           TYPE /BI0/OIRT_MOVINV,
         InfoObject: 0RT_MOVADJ Movement Type is Stock Adjustment.
            RT_MOVADJ           TYPE /BI0/OIRT_MOVADJ,
         InfoObject: 0RSL_STMAT Structured Article.
            RSL_STMAT           TYPE /BI0/OIRSL_STMAT,
         InfoObject: 0RT_MOVRET Movement Type is Return.
            RT_MOVRET           TYPE /BI0/OIRT_MOVRET,
         InfoObject: 0RSL_STAUTO Automatically Completed Component.
            RSL_STAUTO           TYPE /BI0/OIRSL_STAUTO,
         InfoObject: 0RT_MOVTRAN Movement Type is Stock Transfer.
            RT_MOVTRAN           TYPE /BI0/OIRT_MOVTRAN,
         InfoObject: 0RT_MATPOST Transfer Posting from Article to Article.
            RT_MATPOST           TYPE /BI0/OIRT_MATPOST,
         InfoObject: 0RT_SASTSV Share of Business Volume for Set Sales Val
    *ue in Local Crcy.
            RT_SASTSV           TYPE /BI0/OIRT_SASTSV,
         InfoObject: 0RT_SASTST Share of Business Volume for Set with Tax
    *in Local Currency.
            RT_SASTST           TYPE /BI0/OIRT_SASTST,
         InfoObject: 0RMA_XCC RMA Cross-Company Code Stock Transfer.
            RMA_XCC           TYPE /BI0/OIRMA_XCC,
         InfoObject: 0RMA_LNK RMA Stock Transfer Reference Item.
            RMA_LNK           TYPE /BI0/OIRMA_LNK,
         InfoObject: 0RMA_RFLG RMA Relevance Flag.
            RMA_RFLG           TYPE /BI0/OIRMA_RFLG,
         InfoObject: 0RTHFEES Stock Transfer Fees.
            RTHFEES           TYPE /BI0/OIRTHFEES,
         Field: RECORD.
            RECORD           TYPE RSARECORD,
          END   OF tys_SC_1.
        TYPES:
    tyt_SC_1        TYPE STANDARD TABLE OF tys_SC_1
                            WITH NON-UNIQUE DEFAULT KEY.
    $$ begin of global - insert your declaration only below this line  -
    ... "insert your code here
    $$ end of global - insert your declaration only before this line   -
        METHODS
          start_routine
            IMPORTING
              request                  type rsrequest
              datapackid               type rsdatapid
            EXPORTING
              monitor                  type rstr_ty_t_monitors
            CHANGING
              SOURCE_PACKAGE              type tyt_SC_1
            RAISING
              cx_rsrout_abort.
        METHODS
          inverse_start_routine
            IMPORTING
              i_th_fields_outbound         TYPE rstran_t_field_inv
              i_r_selset_outbound          TYPE REF TO cl_rsmds_set
              i_is_main_selection          TYPE rs_bool
              i_r_selset_outbound_complete TYPE REF TO cl_rsmds_set
              i_r_universe_inbound         TYPE REF TO cl_rsmds_universe
            CHANGING
              c_th_fields_inbound          TYPE rstran_t_field_inv
              c_r_selset_inbound           TYPE REF TO cl_rsmds_set
              c_exact                      TYPE rs_bool.
    ENDCLASS.                    "routine DEFINITION
    $$ begin of 2nd part global - insert your code only below this line  *
        TYPES:
          BEGIN OF tys_SC_1_full,
         InfoObject: 0STORNO Stornokennzeichen.
            STORNO           TYPE /BI0/OISTORNO,
         InfoObject: 0RT_PROMO Aktion.
            RT_PROMO           TYPE /BI0/OIRT_PROMO,
         InfoObject: 0VAL_CLASS Bewertungsklasse.
            VAL_CLASS           TYPE /BI0/OIVAL_CLASS,
         InfoObject: 0DOC_DATE Belegdatum.
            DOC_DATE           TYPE /BI0/OIDOC_DATE,
         InfoObject: 0STOCKTYPE Bestandsausprägung.
            STOCKTYPE           TYPE /BI0/OISTOCKTYPE,
         InfoObject: 0STOCKCAT Bestandstypen.
            STOCKCAT           TYPE /BI0/OISTOCKCAT,
         InfoObject: 0PSTNG_DATE Buchungsdatum im Beleg.
            PSTNG_DATE           TYPE /BI0/OIPSTNG_DATE,
         InfoObject: 0COMP_CODE Buchungskreis.
            COMP_CODE           TYPE /BI0/OICOMP_CODE,
         InfoObject: 0BWAPPLNM Anwendungskomponente.
            BWAPPLNM           TYPE /BI0/OIBWAPPLNM,
         InfoObject: 0MOVETYPE Bewegungsart (Bestandsführung).
            MOVETYPE           TYPE /BI0/OIMOVETYPE,
         InfoObject: 0STOCKRELEV BW: Best.Relevanz.
            STOCKRELEV           TYPE /BI0/OISTOCKRELEV,
         InfoObject: 0CPPVLC BW: Einkaufswert in Hauswährung.
            CPPVLC           TYPE /BI0/OICPPVLC,
         InfoObject: 0CPSVLC BW: Verkaufswert in Hauswährung.
            CPSVLC           TYPE /BI0/OICPSVLC,
         InfoObject: 0CPSTLC BW: VerkWmS Hauswährung.
            CPSTLC           TYPE /BI0/OICPSTLC,
         InfoObject: 0CPQUABU BW: Menge in Basismengeneinheit.
            CPQUABU           TYPE /BI0/OICPQUABU,
         InfoObject: 0VAL_TYPE Bewertungsart.
            VAL_TYPE           TYPE /BI0/OIVAL_TYPE,
         InfoObject: 0PROCESSKEY BW:Vorgangsschlüssel.
            PROCESSKEY           TYPE /BI0/OIPROCESSKEY,
         InfoObject: 0BATCH Chargennummer.
            BATCH           TYPE /BI0/OIBATCH,
         InfoObject: 0MATMREA Grund für die Warenbewegung.
            MATMREA           TYPE /BI0/OIMATMREA,
         InfoObject: 0BUS_AREA Geschäftsbereich.
            BUS_AREA           TYPE /BI0/OIBUS_AREA,
         InfoObject: 0COSTCENTER Kostenstelle.
            COSTCENTER           TYPE /BI0/OICOSTCENTER,
         InfoObject: 0SOLD_TO Auftraggeber.
            SOLD_TO           TYPE /BI0/OISOLD_TO,
         InfoObject: 0WHSE_NUM Lagernummer/Lagerkomplex.
            WHSE_NUM           TYPE /BI0/OIWHSE_NUM,
         InfoObject: 0STOR_LOC Lagerort.
            STOR_LOC           TYPE /BI0/OISTOR_LOC,
         InfoObject: 0STRGE_BIN Lagerplatz.
            STRGE_BIN           TYPE /BI0/OISTRGE_BIN,
         InfoObject: 0STRGE_TYPE Lagertyp.
            STRGE_TYPE           TYPE /BI0/OISTRGE_TYPE,
         InfoObject: 0VENDOR Lieferant.
            VENDOR           TYPE /BI0/OIVENDOR,
         InfoObject: 0MATERIAL Material.
            MATERIAL           TYPE /BI0/OIMATERIAL,
         InfoObject: 0DOC_NUM BW: Belegnummer.
            DOC_NUM           TYPE /BI0/OIDOC_NUM,
         InfoObject: 0BASE_UOM Basismengeneinheit.
            BASE_UOM           TYPE /BI0/OIBASE_UOM,
         InfoObject: 0DOC_YEAR BW: Belegjahr.
            DOC_YEAR           TYPE /BI0/OIDOC_YEAR,
         InfoObject: 0PROFIT_CTR Profit Center.
            PROFIT_CTR           TYPE /BI0/OIPROFIT_CTR,
         InfoObject: 0DCINDIC Soll-/Haben-Kennzeichen.
            DCINDIC           TYPE /BI0/OIDCINDIC,
         InfoObject: 0LOC_CURRCY Hauswährung.
            LOC_CURRCY           TYPE /BI0/OILOC_CURRCY,
         InfoObject: 0PLANT Werk.
            PLANT           TYPE /BI0/OIPLANT,
         InfoObject: 0FISCVARNT Geschäftsjahresvariante.
            FISCVARNT           TYPE /BI0/OIFISCVARNT,
         InfoObject: 0CPNOITEMS BW: Anzahl Vorgänge.
            CPNOITEMS           TYPE /BI0/OICPNOITEMS,
         InfoObject: 0CO_AREA Kostenrechnungskreis.
            CO_AREA           TYPE /BI0/OICO_AREA,
         InfoObject: 0DOC_ITEM BW: Belegpositionsnummer.
            DOC_ITEM           TYPE /BI0/OIDOC_ITEM,
         InfoObject: 0VALUE_LC Betrag in Hauswährung.
            VALUE_LC           TYPE /BI0/OIVALUE_LC,
         InfoObject: 0COORDER Auftragsnummer.
            COORDER           TYPE /BI0/OICOORDER,
         InfoObject: 0QUANT_B Menge in Basismengeneinheiten.
            QUANT_B           TYPE /BI0/OIQUANT_B,
         InfoObject: 0MOVE_PLANT Empfangendes/Abgebendes Werk.
            MOVE_PLANT           TYPE /BI0/OIMOVE_PLANT,
         InfoObject: 0RECORDMODE BW Deltaverfahren: Update Modus.
            RECORDMODE           TYPE RODMUPDMOD,
    *******************Commented based on oss note1052648*****************************
         InfoObject: 0RT_RMAPIDA RMA Inventurdatum.
           RT_RMAPIDA           TYPE /BI0/OIRT_RMAPIDA,
    End Commented based on oss note1052648************************
         InfoObject: 0BWCOUNTER Zusätzliches Schlüsselfeld Umbewertungsbel
    *egsatz.
            BWCOUNTER           TYPE /BI0/OIBWCOUNTER,
         InfoObject: 0INDSPECSTK Kennzeichen Bewertung Sonderbestand.
            INDSPECSTK           TYPE /BI0/OIINDSPECSTK,
         InfoObject: 0GN_R3_SSY Quellsystem der R/3 Entität.
            GN_R3_SSY           TYPE /BI0/OIGN_R3_SSY,
         InfoObject: 0RT_MOVINV Bewegungsart ist Inventur.
            RT_MOVINV           TYPE /BI0/OIRT_MOVINV,
         InfoObject: 0RT_MOVADJ Bewegungsart ist Bestandskorrektur.
            RT_MOVADJ           TYPE /BI0/OIRT_MOVADJ,
         InfoObject: 0RSL_STMAT Strukturierter Artikel.
            RSL_STMAT           TYPE /BI0/OIRSL_STMAT,
         InfoObject: 0RT_MOVRET Bewegungsart ist Retoure.
            RT_MOVRET           TYPE /BI0/OIRT_MOVRET,
         InfoObject: 0RSL_STAUTO Automatisch ergänzte Komponente.
            RSL_STAUTO           TYPE /BI0/OIRSL_STAUTO,
         InfoObject: 0RT_MOVTRAN Bewegungsart ist Umlagerung.
            RT_MOVTRAN           TYPE /BI0/OIRT_MOVTRAN,
         InfoObject: 0RT_MATPOST Umbuchung Artikel an Artikel.
            RT_MATPOST           TYPE /BI0/OIRT_MATPOST,
         InfoObject: 0RT_SASTSV Umsatzanteil am Set Verkaufswert in Hauswä
    *hrung.
            RT_SASTSV           TYPE /BI0/OIRT_SASTSV,
         InfoObject: 0RT_SASTST Umsatzanteil am Set Verkaufswert mit Steue
    *r in Hauswährung.
            RT_SASTST           TYPE /BI0/OIRT_SASTST,
    **********************Added as per note1052648*****************************************
         InfoObject: 0RMA_XCC RMA Cross-Company Code Stock Transfer.
            RMA_XCC           TYPE /BI0/OIRMA_XCC,
         InfoObject: 0RMA_LNK RMA Stock Transfer Reference Item.
            RMA_LNK           TYPE /BI0/OIRMA_LNK,
         InfoObject: 0RMA_RFLG RMA Relevance Flag.
            RMA_RFLG           TYPE /BI0/OIRMA_RFLG,
         InfoObject: 0RTHFEES Stock Transfer Fees.
            RTHFEES           TYPE /BI0/OIRTHFEES,
    **********************End Added as per note1052648**************************************
         Field: RECORD.
            RECORD           TYPE RSARECORD,
            END   OF tys_SC_1_full.
        TYPES:
    tyt_SC_1_full        TYPE STANDARD TABLE OF tys_SC_1_full
                            WITH NON-UNIQUE DEFAULT KEY.
        TYPES:
          BEGIN OF tys_TG_1_full,
         InfoObject: 0CHNGID Änderungslauf ID.
            CHNGID           TYPE /BI0/OICHNGID,
         InfoObject: 0RECORDTP Satztyp.
            RECORDTP           TYPE /BI0/OIRECORDTP,
         InfoObject: 0REQUID Request ID.
            REQUID           TYPE /BI0/OIREQUID,
         InfoObject: 0CALDAY Kalendertag.
            CALDAY           TYPE /BI0/OICALDAY,
         InfoObject: 0CALMONTH Kalenderjahr / Monat.
            CALMONTH           TYPE /BI0/OICALMONTH,
         InfoObject: 0CALWEEK Kalenderjahr / Woche.
            CALWEEK           TYPE /BI0/OICALWEEK,
         InfoObject: 0CALYEAR Kalenderjahr.
            CALYEAR           TYPE /BI0/OICALYEAR,
         InfoObject: 0MATERIAL Material.
            MATERIAL           TYPE /BI0/OIMATERIAL,
         InfoObject: 0PLANT Werk.
            PLANT           TYPE /BI0/OIPLANT,
         InfoObject: 0STOR_LOC Lagerort.
            STOR_LOC           TYPE /BI0/OISTOR_LOC,
         InfoObject: 0BATCH Chargennummer.
            BATCH           TYPE /BI0/OIBATCH,
         InfoObject: 0STOCKTYPE Bestandsausprägung.
            STOCKTYPE           TYPE /BI0/OISTOCKTYPE,
         InfoObject: 0STOCKCAT Bestandstypen.
            STOCKCAT           TYPE /BI0/OISTOCKCAT,
         InfoObject: 0GN_VENDOR Lieferant.
            GN_VENDOR           TYPE /BI0/OIGN_VENDOR,
         InfoObject: 0RECVS_VAL Zugangswert Bewerteter Bestand.
            RECVS_VAL           TYPE /BI0/OIRECVS_VAL,
         InfoObject: 0ISSVS_VAL Abgangswert Bewerteter Bestand.
            ISSVS_VAL           TYPE /BI0/OIISSVS_VAL,
         InfoObject: 0ISSBLOSTCK Abgangsmenge Gesperrter Bestand.
            ISSBLOSTCK           TYPE /BI0/OIISSBLOSTCK,
         InfoObject: 0ISSCNSSTCK Abgangsmenge Konsignationsbestand.
            ISSCNSSTCK           TYPE /BI0/OIISSCNSSTCK,
         InfoObject: 0ISSQMSTCK Abgangsmenge Qualitätsbestand.
            ISSQMSTCK           TYPE /BI0/OIISSQMSTCK,
         InfoObject: 0ISSTRANSST Abgangsmenge Transitbestand.
            ISSTRANSST           TYPE /BI0/OIISSTRANSST,
         InfoObject: 0RECBLOSTCK Zugangsmenge Gesperrter Bestand.
            RECBLOSTCK           TYPE /BI0/OIRECBLOSTCK,
         InfoObject: 0RECCNSSTCK Zugangsmenge Konsignationsbestand.
            RECCNSSTCK           TYPE /BI0/OIRECCNSSTCK,
         InfoObject: 0RECQMSTCK Zugangsmenge Qualitätsbestand.
            RECQMSTCK           TYPE /BI0/OIRECQMSTCK,
         InfoObject: 0RECTRANSST Zugangsmenge Transitbestand.
            RECTRANSST           TYPE /BI0/OIRECTRANSST,
         InfoObject: 0ISSSCRP Abgangsmenge Ausschuss.
            ISSSCRP           TYPE /BI0/OIISSSCRP,
         InfoObject: 0ISSVALSCRP Abgangswert Ausschuss.
            ISSVALSCRP           TYPE /BI0/OIISSVALSCRP,
         InfoObject: 0RECTOTSTCK Zugangsmenge Gesamt Bestand.
            RECTOTSTCK           TYPE /BI0/OIRECTOTSTCK,
         InfoObject: 0ISSTOTSTCK Abgangsmenge Gesamtbestand.
            ISSTOTSTCK           TYPE /BI0/OIISSTOTSTCK,
         InfoObject: 0ISSVALSTCK Abgangsmenge Bewerteter Bestand.
            ISSVALSTCK           TYPE /BI0/OIISSVALSTCK,
         InfoObject: 0RECVALSTCK Zugangsmenge Bewerteter Bestand.
            RECVALSTCK           TYPE /BI0/OIRECVALSTCK,
         InfoObject: 0VENCONCON Verbrauchswerte Lieferantenkonsignationsbe
    *stand.
            VENCONCON           TYPE /BI0/OIVENCONCON,
         InfoObject: 0LOC_CURRCY Hauswährung.
            LOC_CURRCY           TYPE /BI0/OILOC_CURRCY,
         InfoObject: 0BASE_UOM Basismengeneinheit.
            BASE_UOM           TYPE /BI0/OIBASE_UOM,
         Field: RECORD Nummer des Datensatzes.
            RECORD           TYPE RSARECORD,
          END   OF tys_TG_1_full.
        TYPES:
          BEGIN OF tys_SC_1__RULE_9,
         InfoObject: 0BWAPPLNM Anwendungskomponente.
            BWAPPLNM           TYPE /BI0/OIBWAPPLNM,
         InfoObject: 0CPQUABU BW: Menge in Basismengeneinheit.
            CPQUABU           TYPE /BI0/OICPQUABU,
         InfoObject: 0PROCESSKEY BW:Vorgangsschlüssel.
            PROCESSKEY           TYPE /BI0/OIPROCESSKEY,
         InfoObject: 0STOCKCAT Bestandstypen.
            STOCKCAT           TYPE /BI0/OISTOCKCAT,
         InfoObject: 0STOCKRELEV BW: Best.Relevanz.
            STOCKRELEV           TYPE /BI0/OISTOCKRELEV,
         InfoObject: 0STOCKTYPE Bestandsausprägung.
            STOCKTYPE           TYPE /BI0/OISTOCKTYPE,
         InfoObject: 0BASE_UOM Basismengeneinheit.
            BASE_UOM           TYPE /BI0/OIBASE_UOM,
          END   OF tys_SC_1__RULE_9.
        TYPES:
          BEGIN OF tys_SC_1__RULE_10,
         InfoObject: 0BWAPPLNM Anwendungskomponente.
            BWAPPLNM           TYPE /BI0/OIBWAPPLNM,
         InfoObject: 0CPQUABU BW: Menge in Basismengeneinheit.
            CPQUABU           TYPE /BI0/OICPQUABU,
         InfoObject: 0PROCESSKEY BW:Vorgangsschlüssel.
            PROCESSKEY           TYPE /BI0/OIPROCESSKEY,
         InfoObject: 0STOCKCAT Bestandstypen.
            STOCKCAT           TYPE /BI0/OISTOCKCAT,
         InfoObject: 0STOCKRELEV BW: Best.Relevanz.
            STOCKRELEV           TYPE /BI0/OISTOCKRELEV,
         InfoObject: 0STOCKTYPE Bestandsausprägung.
            STOCKTYPE           TYPE /BI0/OISTOCKTYPE,
         InfoObject: 0BASE_UOM Basismengeneinheit.
            BASE_UOM           TYPE /BI0/OIBASE_UOM,
          END   OF tys_SC_1__RULE_10.
        TYPES:
          BEGIN OF tys_SC_1__RULE_11,
         InfoObject: 0GN_R3_SSY Quellsystem der R/3 Entität.
            GN_R3_SSY           TYPE /BI0/OIGN_R3_SSY,
         InfoObject: 0STOCKCAT Bestandstypen.
            STOCKCAT           TYPE /BI0/OISTOCKCAT,
         InfoObject: 0VENDOR Lieferant.
            VENDOR           TYPE /BI0/OIVENDOR,
          END   OF tys_SC_1__RULE_11.
        TYPES:
          BEGIN OF tys_SC_1__RULE_12,
         InfoObject: 0BWAPPLNM Anwendungskomponente.
            BWAPPLNM           TYPE /BI0/OIBWAPPLNM,
         InfoObject: 0CPPVLC BW: Einkaufswert in Hauswährung.
            CPPVLC           TYPE /BI0/OICPPVLC,
         InfoObject: 0INDSPECSTK Kennzeichen Bewertung Sonderbestand.
            INDSPECSTK           TYPE /BI0/OIINDSPECSTK,
         InfoObject: 0PROCESSKEY BW:Vorgangsschlüssel.
            PROCESSKEY           TYPE /BI0/OIPROCESSKEY,
         InfoObject: 0STOCKCAT Bestandstypen.
            STOCKCAT           TYPE /BI0/OISTOCKCAT,
         InfoObject: 0STOCKRELEV BW: Best.Relevanz.
            STOCKRELEV           TYPE /BI0/OISTOCKRELEV,
         InfoObject: 0LOC_CURRCY Hauswährung.
            LOC_CURRCY           TYPE /BI0/OILOC_CURRCY,
          END   OF tys_SC_1__RULE_12.
        TYPES:
          BEGIN OF tys_SC_1__RULE_13,
         InfoObject: 0BWAPPLNM Anwendungskomponente.
            BWAPPLNM           TYPE /BI0/OIBWAPPLNM,
         InfoObject: 0CPPVLC BW: Einkaufswert in Hauswährung.
            CPPVLC           TYPE /BI0/OICPPVLC,
         InfoObject: 0INDSPECSTK Kennzeichen Bewertung Sonderbestand.
            INDSPECSTK           TYPE /BI0/OIINDSPECSTK,
         InfoObject: 0PROCESSKEY BW:Vorgangsschlüssel.
            PROCESSKEY           TYPE /BI0/OIPROCESSKEY,
         InfoObject: 0STOCKCAT Bestandstypen.
            STOCKCAT           TYPE /BI0/OISTOCKCAT,
         InfoObject: 0STOCKRELEV BW: Best.Relevanz.
            STOCKRELEV           TYPE /BI0/OISTOCKRELEV,
         InfoObject: 0LOC_CURRCY Hauswährung.
            LOC_CURRCY           TYPE /BI0/OILOC_CURRCY,
          END   OF tys_SC_1__RULE_13.
        TYPES:
          BEGIN OF tys_SC_1__RULE_15,
         InfoObject: 0GN_R3_SSY Quellsystem der R/3 Entität.
            GN_R3_SSY           TYPE /BI0/OIGN_R3_SSY,
         InfoObject: 0STOCKCAT Bestandstypen.
            STOCKCAT           TYPE /BI0/OISTOCKCAT,
         InfoObject: 0STOCKTYPE Bestandsausprägung.
            STOCKTYPE           TYPE /BI0/OISTOCKTYPE,
         InfoObject: 0VENDOR Lieferant.
            VENDOR           TYPE /BI0/OIVENDOR,
          END   OF tys_SC_1__RULE_15.
        TYPES:
          BEGIN OF tys_SC_1__RULE_19,
         InfoObject: 0BWAPPLNM Anwendungskomponente.
            BWAPPLNM           TYPE /BI0/OIBWAPPLNM,
         InfoObject: 0CPQUABU BW: Menge in Basismengeneinheit.
            CPQUABU           TYPE /BI0/OICPQUABU,
         InfoObject: 0PROCESSKEY BW:Vorgangsschlüssel.
            PROCESSKEY           TYPE /BI0/OIPROCESSKEY,
         InfoObject: 0STOCKRELEV BW: Best.Relevanz.
            STOCKRELEV           TYPE /BI0/OISTOCKRELEV,
         InfoObject: 0BASE_UOM Basismengeneinheit.
            BASE_UOM           TYPE /BI0/OIBASE_UOM,
          END   OF tys_SC_1__RULE_19.
        TYPES:
          BEGIN OF tys_SC_1__RULE_20,
         InfoObject: 0BWAPPLNM Anwendungskomponente.
            BWAPPLNM           TYPE /BI0/OIBWAPPLNM,
         InfoObject: 0CPQUABU BW: Menge in Basismengeneinheit.
            CPQUABU           TYPE /BI0/OICPQUABU,
         InfoObject: 0PROCESSKEY BW:Vorgangsschlüssel.
            PROCESSKEY           TYPE /BI0/OIPROCESSKEY,
         InfoObject: 0STOCKRELEV BW: Best.Relevanz.
            STOCKRELEV           TYPE /BI0/OISTOCKRELEV,
         InfoObject: 0BASE_UOM Basismengeneinheit.
            BASE_UOM           TYPE /BI0/OIBASE_UOM,
          END   OF tys_SC_1__RULE_20.
        TYPES:
          BEGIN OF tys_SC_1__RULE_21,
         InfoObject: 0BWAPPLNM Anwendungskomponente.
            BWAPPLNM           TYPE /BI0/OIBWAPPLNM,
         InfoObject: 0CPQUABU BW: Menge in Basismengeneinheit.
            CPQUABU           TYPE /BI0/OICPQUABU,
         InfoObject: 0INDSPECSTK Kennzeichen Bewertung Sonderbestand.
            INDSPECSTK           TYPE /BI0/OIINDSPECSTK,
         InfoObject: 0PROCESSKEY BW:Vorgangsschlüssel.
            PROCESSKEY           TYPE /BI0/OIPROCESSKEY,
         InfoObject: 0STOCKCAT Bestandstypen.
            STOCKCAT           TYPE /BI0/OISTOCKCAT,
         InfoObject: 0STOCKRELEV BW: Best.Relevanz.
            STOCKRELEV           TYPE /BI0/OISTOCKRELEV,
         InfoObject: 0BASE_UOM Basismengeneinheit.
            BASE_UOM           TYPE /BI0/OIBASE_UOM,
          END   OF tys_SC_1__RULE_21.
        TYPES:
          BEGIN OF tys_SC_1__RULE_22,
         InfoObject: 0BWAPPLNM Anwendungskomponente.
            BWAPPLNM           TYPE /BI0/OIBWAPPLNM,
         InfoObject: 0CPQUABU BW: Menge in Basismengeneinheit.
            CPQUABU           TYPE /BI0/OICPQUABU,
         InfoObject: 0INDSPECSTK Kennzeichen Bewertung Sonderbestand.
            INDSPECSTK           TYPE /BI0/OIINDSPECSTK,
         InfoObject: 0PROCESSKEY BW:Vorgangsschlüssel.
            PROCESSKEY           TYPE /BI0/OIPROCESSKEY,
         InfoObject: 0STOCKCAT Bestandstypen.
            STOCKCAT           TYPE /BI0/OISTOCKCAT,
         InfoObject: 0STOCKRELEV BW: Best.Relevanz.
            STOCKRELEV           TYPE /BI0/OISTOCKRELEV,
         InfoObject: 0BASE_UOM Basismengeneinheit.
            BASE_UOM           TYPE /BI0/OIBASE_UOM,
          END   OF tys_SC_1__RULE_22.
        TYPES:
          BEGIN OF tys_SC_1__RULE_25,
         InfoObject: 0GN_R3_SSY Quellsystem der R/3 Entität.
            GN_R3_SSY           TYPE /BI0/OIGN_R3_SSY,
         InfoObject: 0STOCKCAT Bestandstypen.
            STOCKCAT           TYPE /BI0/OISTOCKCAT,
         InfoObject: 0STOCKTYPE Bestandsausprägung.
            STOCKTYPE           TYPE /BI0/OISTOCKTYPE,
         InfoObject: 0VENDOR Lieferant.
            VENDOR           TYPE /BI0/OIVENDOR,
          END   OF tys_SC_1__RULE_25.
        TYPES:
          BEGIN OF tys_SC_1__RULE_31,
         InfoObject: 0BWAPPLNM Anwendungskomponente.
            BWAPPLNM           TYPE /BI0/OIBWAPPLNM,
         InfoObject: 0CPPVLC BW: Einkaufswert in Hauswährung.
            CPPVLC           TYPE /BI0/OICPPVLC,
         InfoObject: 0PROCESSKEY BW:Vorgangsschlüssel.
            PROCESSKEY           TYPE /BI0/OIPROCESSKEY,
         InfoObject: 0STOCKCAT Bestandstypen.
            STOCKCAT           TYPE /BI0/OISTOCKCAT,
         InfoObject: 0STOCKRELEV BW: Best.Relevanz.
            STOCKRELEV           TYPE /BI0/OISTOCKRELEV,
         InfoObject: 0LOC_CURRCY Hauswährung.
            LOC_CURRCY           TYPE /BI0/OILOC_CURRCY,
          END   OF tys_SC_1__RULE_31.
        TYPES:
          BEGIN OF tys_SC_1__RULE_37,
         InfoObject: 0BWAPPLNM Anwendungskomponente.
            BWAPPLNM           TYPE /BI0/OIBWAPPLNM,
         InfoObject: 0CPQUABU BW: Menge in Basismengeneinheit.
            CPQUABU           TYPE /BI0/OICPQUABU,
         InfoObject: 0PROCESSKEY BW:Vorgangsschlüssel.
            PROCESSKEY           TYPE /BI0/OIPROCESSKEY,
         InfoObject: 0STOCKCAT Bestandstypen.
            STOCKCAT           TYPE /BI0/OISTOCKCAT,
         InfoObject: 0STOCKRELEV BW: Best.Relevanz.
            STOCKRELEV           TYPE /BI0/OISTOCKRELEV,
         InfoObject: 0STOCKTYPE Bestandsausprägung.
            STOCKTYPE           TYPE /BI0/OISTOCKTYPE,
         InfoObject: 0BASE_UOM Basismengeneinheit.
            BASE_UOM           TYPE /BI0/OIBASE_UOM,
          END   OF tys_SC_1__RULE_37.
        TYPES:
          BEGIN OF tys_SC_1__RULE_38,
         InfoObject: 0BWAPPLNM Anwendungskomponente.
            BWAPPLNM           TYPE /BI0/OIBWAPPLNM,
         InfoObject: 0CPQUABU BW: Menge in Basismengeneinheit.
            CPQUABU           TYPE /BI0/OICPQUABU,
         InfoObject: 0PROCESSKEY BW:Vorgangsschlüssel.
            PROCESSKEY           TYPE /BI0/OIPROCESSKEY,
         InfoObject: 0STOCKCAT Bestandstypen.
            STOCKCAT           TYPE /BI0/OISTOCKCAT,
         InfoObject: 0STOCKRELEV BW: Best.Relevanz.
            STOCKRELEV           TYPE /BI0/OISTOCKRELEV,
         InfoObject: 0STOCKTYPE Bestandsausprägung.
            STOCKTYPE           TYPE /BI0/OISTOCKTYPE,
         InfoObject: 0BASE_UOM Basismengeneinheit.
            BASE_UOM           TYPE /BI0/OIBASE_UOM,
          END   OF tys_SC_1__RULE_38.
        TYPES:
          BEGIN OF tys_SC_1__RULE_39,
         InfoObject: 0BWAPPLNM Anwendungskomponente.
            BWAPPLNM           TYPE /BI0/OIBWAPPLNM,
         InfoObject: 0CPQUABU BW: Menge in Basismengeneinheit.
            CPQUABU           TYPE /BI0/OICPQUABU,
         InfoObject: 0PROCESSKEY BW:Vorgangsschlüssel.
            PROCESSKEY           TYPE /BI0/OIPROCESSKEY,
         InfoObject: 0STOCKRELEV BW: Best.Relevanz.
            STOCKRELEV           TYPE /BI0/OISTOCKRELEV,
         InfoObject: 0STOCKTYPE Bestandsausprägung.
            STOCKTYPE           TYPE /BI0/OISTOCKTYPE,
         InfoObject: 0BASE_UOM Basismengeneinheit.
            BASE_UOM           TYPE /BI0/OIBASE_UOM,
          END   OF tys_SC_1__RULE_39.
        TYPES:
          BEGIN OF tys_SC_1__RULE_40,
         InfoObject: 0BWAPPLNM Anwendungskomponente.
            BWAPPLNM           TYPE /BI0/OIBWAPPLNM,
         InfoObject: 0CPQUABU BW: Menge in Basismengeneinheit.
            CPQUABU           TYPE /BI0/OICPQUABU,
         InfoObject: 0PROCESSKEY BW:Vorgangsschlüssel.
            PROCESSKEY           TYPE /BI0/OIPROCESSKEY,
         InfoObject: 0STOCKCAT Bestandstypen.
            STOCKCAT           TYPE /BI0/OISTOCKCAT,
         InfoObject: 0STOCKRELEV BW: Best.Relevanz.
            STOCKRELEV           TYPE /BI0/OISTOCKRELEV,
         InfoObject: 0STOCKTYPE Bestandsausprägung.
            STOCKTYPE           TYPE /BI0/OISTOCKTYPE,
         InfoObject: 0BASE_UOM Basismengeneinheit.
            BASE_UOM           TYPE /BI0/OIBASE_UOM,
          END   OF tys_SC_1__RULE_40.
        TYPES:
          BEGIN OF tys_SC_1__RULE_41,
         InfoObject: 0BWAPPLNM Anwendungskomponente.
            BWAPPLNM           TYPE /BI0/OIBWAPPLNM,
         InfoObject: 0CPQUABU BW: Menge in Basismengeneinheit.
            CPQUABU           TYPE /BI0/OICPQUABU,
         InfoObject: 0PROCESSKEY BW:Vorgangsschlüssel.
            PROCESSKEY           TYPE /BI0/OIPROCESSKEY,
         InfoObject: 0STOCKCAT Bestandstypen.
            STOCKCAT           TYPE /BI0/OISTOCKCAT,
         InfoObject: 0STOCKRELEV BW: Best.Relevanz.
            STOCKRELEV           TYPE /BI0/OISTOCKRELEV,
         InfoObject: 0STOCKTYPE Bestandsausprägung.
            STOCKTYPE           TYPE /BI0/OISTOCKTYPE,
         InfoObject: 0BASE_UOM Basismengeneinheit.
            BASE_UOM           TYPE /BI0/OIBASE_UOM,
          END   OF tys_SC_1__RULE_41.
        TYPES:
          BEGIN OF tys_SC_1__RULE_42,
         InfoObject: 0BWAPPLNM Anwendungskomponente.
            BWAPPLNM           TYPE /BI0/OIBWAPPLNM,
         InfoObject: 0CPQUABU BW: Menge in Basismengeneinheit.
            CPQUABU           TYPE /BI0/OICPQUABU,
         InfoObject: 0PROCESSKEY BW:Vorgangsschlüssel.
            PROCESSKEY           TYPE /BI0/OIPROCESSKEY,
         InfoObject: 0STOCKRELEV BW: Best.Relevanz.
            STOCKRELEV           TYPE /BI0/OISTOCKRELEV,
         InfoObject: 0STOCKTYPE Bestandsausprägung.
            STOCKTYPE           TYPE /BI0/OISTOCKTYPE,
         InfoObject: 0BASE_UOM Basismengeneinheit.
            BASE_UOM           TYPE /BI0/OIBASE_UOM,
          END   OF tys_SC_1__RULE_42.
        TYPES:
          BEGIN OF tys_SC_1__RULE_43,
         InfoObject: 0BWAPPLNM Anwendungskomponente.
            BWAPPLNM           TYPE /BI0/OIBWAPPLNM,
         InfoObject: 0CPQUABU BW: Menge in Basismengeneinheit.
            CPQUABU           TYPE /BI0/OICPQUABU,
         InfoObject: 0MOVETYPE Bewegungsart (Bestandsführung).
            MOVETYPE           TYPE /BI0/OIMOVETYPE,
         InfoObject: 0BASE_UOM Basismengeneinheit.
            BASE_UOM           TYPE /BI0/OIBASE_UOM,
          END   OF tys_SC_1__RULE_43.
        TYPES:
          BEGIN OF tys_SC_1__RULE_51,
         InfoObject: 0BWAPPLNM Anwendungskomponente.
            BWAPPLNM           TYPE /BI0/OIBWAPPLNM,
         InfoObject: 0CPPVLC BW: Einkaufswert in Hauswährung.
            CPPVLC           TYPE /BI0/OICPPVLC,
         InfoObject: 0MOVETYPE Bewegungsart (Bestandsführung).
            MOVETYPE           TYPE /BI0/OIMOVETYPE,
         InfoObject: 0LOC_CURRCY Hauswährung.
            LOC_CURRCY           TYPE /BI0/OILOC_CURRCY,
          END   OF tys_SC_1__RULE_51.
    Additional types for start routine interface
      TYPES:
        data_package_structure type tys_SC_1_full.
    Additional declaration for update rule interface
      DATA:
        MONITOR       type standard table of rsmonitor  WITH HEADER LINE,
        MONITOR_RECNO type standard table of rsmonitors WITH HEADER LINE,
        RECORD_NO     LIKE SY-TABIX,
        RECORD_ALL    LIKE SY-TABIX,
        SOURCE_SYSTEM LIKE RSUPDSIMULH-LOGSYS.
    global definitions from update rules
    INCLUDE rsbctgn_top.
    INCLUDE rsbctgn_update_rules.
    FORM routine_9998
      TABLES DATA_PACKAGE TYPE tyt_SC_1_full
      CHANGING
        ABORT          LIKE sy-subrc
      RAISING
        cx_sy_arithmetic_error
        cx_sy_conversion_error.
    init variables
    fill the internal table "MONITOR", to make monitor entries
    see OSS note 571669
      LOOP AT DATA_PACKAGE.
        IF DATA_PACKAGE-stockcat EQ 'V' OR
           DATA_PACKAGE-stocktype EQ 'V'.
          DELETE DATA_PACKAGE.
        ENDIF.
      ENDLOOP.
    if abort is not equal zero, the update process will be canceled
      ABORT = 0.
    ENDFORM.                    "routine_9998
    FORM routine_0012
      USING
        COMM_STRUCTURE type tys_SC_1__RULE_9
      CHANGING
        RESULT         TYPE tys_TG_1_full-ISSCNSSTCK
        RETURNCODE     LIKE sy-subrc
        ABORT          LIKE sy-subrc
      RAISING
        cx_sy_arithmetic_error
        cx_sy_conversion_error.
    init variables
    fill the internal table "MONITOR", to make monitor entries
    only goods issue is considered
      IF ( COMM_STRUCTURE-processkey EQ '100'   "Other Issues
        OR COMM_STRUCTURE-processkey EQ '101'   "Returns / Vendor
        OR COMM_STRUCTURE-processkey EQ '104'   "Material Transfer
        OR COMM_STRUCTURE-processkey EQ '105'   "Stock Adjustment InvD
        OR COMM_STRUCTURE-processkey EQ '106'   "Stock Adjustment Other
        OR COMM_STRUCTURE-processkey EQ '110' ) "Issue from Stock Transfer
       AND COMM_STRUCTURE-bwapplnm EQ 'MM'
    only movements which are relevant for stock control
       AND COMM_STRUCTURE-stockrelev EQ '1'
       AND COMM_STRUCTURE-cpquabu <> 0.
    only consignment stock is considered
        CASE COMM_STRUCTURE-stockcat.
          WHEN 'K'.
            RESULT = COMM_STRUCTURE-cpquabu.
            RETURNCODE = 0.
          WHEN space.
            IF COMM_STRUCTURE-stocktype CA 'KLM'.
              RESULT = COMM_STRUCTURE-cpquabu.
              RETURNCODE = 0.
            ELSE.
              RETURNCODE = 4.
            ENDIF.
          WHEN OTHERS.
            RETURNCODE = 4.
        ENDCASE.
      ELSE.
    if the returncode is not equal zero, the result will not be updated
        RETURNCODE = 4.
      ENDIF.
    if abort is not equal zero, the update process will be canceled
      ABORT = 0.
    ENDFORM.                    "routine_0012
    FORM routine_0014
      USING
        COMM_STRUCTURE type tys_SC_1__RULE_10
      CHANGING
        RESULT         TYPE tys_TG_1_full-RECCNSSTCK
        RETURNCODE     LIKE sy-subrc
        ABORT          LIKE sy-subrc
      RAISING
        cx_sy_arithmetic_error
        cx_sy_conversion_error.
    init variables
    fill the internal table "MONITOR", to make monitor entries
    only goods receipt is considered
      IF ( COMM_STRUCTURE-processkey EQ '000'   "Other Receipts
        OR COMM_STRUCTURE-processkey EQ '001'   "Goods Receipt / Vendor
        OR COMM_STRUCTURE-processkey EQ '004'   "Material Transfer
        OR COMM_STRUCTURE-processkey EQ '005'   "Stock Adjustment InvD
        OR COMM_STRUCTURE-processkey EQ '006'   "Stock Adjustment Other
        OR COMM_STRUCTURE-processkey EQ '010' ) "Receipt from Stock Transfer
       AND COMM_STRUCTURE-bwapplnm EQ 'MM'
    only movements which are relevant for stock control
       AND COMM_STRUCTURE-stockrelev EQ '1'
       AND COMM_STRUCTURE-cpquabu <> 0.
    only consignment stock is considered
        CASE COMM_STRUCTURE-stockcat.
          WHEN 'K'.
            RESULT = COMM_STRUCTURE-cpquabu.
            RETURNCODE = 0.
          WHEN space.
            IF COMM_STRUCTURE-stocktype CA 'KLM'.
              RESULT = COMM_STRUCTURE-cpquabu.
              RETURNCODE = 0.
            ELSE.
              RETURNCODE = 4.
            ENDIF.
          WHEN OTHERS.
            RETURNCODE = 4.
        ENDCASE.
      ELSE.
    if the returncode is not equal zero, the result will not be updated
        RETURNCODE = 4.
      ENDIF.

  • Issue in COPA Report Creation

    Dear All,
    I ave an issue in creation of COPA repor in KE30
    We have created all P&L item as cost element except
    1.Change in WIP for WIP calculation in Product Costing
    2. Price Difference (OBYC- PRD) Variance will be calculated from settlement profile
    Values in COPA are
    1.     VV001  - Quantity (KWBRUM) Quantity field
    2.     VV002 u2013 Price  (PR00) Revenue account of sales (Cost Category 11)
    3.     VV002 -  Material Cost-COGS (VPRS)
    4.     VV003 -  Discount Given (SD Condition)  (Cost Category 12)
    5.     VV005 u2013 Fright (SD Condition)  (Cost Category 12)
    6.     VV005 u2013 Misc Exp (SD  Condition) (Cost Category 12)
    7.     VV006 -  Consumption and Cost of Production, Revaluation, inv diff account
    8.     VV007 u2013 admin expenses
    9.     VV008  - Employees cost
    10.     VV009 u2013 financial cost (interest paid etc deprecation cost, audit exp)
    11.     VV010 u2013 Settlement of Variances of Production order (from settlement profile)
    12.     VV011 - Other income GL accounts (including Exch Rate Diff, profit on sale of asset etc)
    From VV005 to VV009 all the GL account included are created as primary cost element (C category 01)
    and assigned in OKB9 as transfer to PA structure and assigned in PA transfer FI (direct posting form FI)
    VV011 u2013 all the GL account created as Revenue (Cost Category 11)
    Issue we are facing
    1. In Consumption and Cost of Production GL account (Movement type 101 and 261 from production order ) we are not
    able to generate Profit analysis document.
    2. Price difference also come in picture at the time of Stock transfer and Price diff GL account is not created as cost element and how to flow that in copa, price difference from settlement will come from settlement profile.
    Format we have created for COPA report is like
    1.Quantity Field
    2.Selling Price  (PR00)
    3 Material Cost (VPRS)
    4 Discount Given
    5. Fright
    6. Misc Exp
    7. Consumption and Cost of Production, Revaluation, inv diff account
    8 admin expenses
    9. Employees cost
    10. financial cost
    11 Settlement of Variances of Production order
    12. Other income
    13 Net Profit (Calculated Values ) ( 2- 3-4-5-6-7-8-9-10-11+12)
    Is this a correct logic I applied kindly suggest.
    Regards
    Bittu

    Dear All,
    Any suggestion..
    Bittu

  • Stock Issue/Receipt Values in 0IC_C03 not matchin with MC.9

    Hi Experts,
    We are facing a certain mismatch problem in our Inventory Cube
    (0IC_C03) stock issue and receipt values. They are showing a huge
    difference with the issue and receipt values in ECC Report MC.9.
    Also please note that the Quantities in the cube are matching exactly
    with MC.9 but not values.
    On further search , we also noted that the Plant wise Values and
    quantities in BW are exactly matching with certain infostructures
    (S031, S033) but not with MC.9 in ECC Production.
    Can anyone please let us know how can we check the plant wise
    issue/Receipt values  ?
    Also, We replicated the same senario in Quality system and did an
    inventory
    cube Reload . But it still showed the same discrepencies from MC.9 for the given material and period.
    Regards

    Dear AL,
    There is not failed request and the cube, and the loading is correct.
    Also we replicated the same on Quality, and did a complete Reload for the cube and it still gave the same difference.
    Kindly let me know how can we check the issue and recept values from PSA of Revaluations Extractor??
    Dear Shashank,
    We are using standard logistics extractor 2LIS_03_UM for the cube.
    Along with 2LIS_03_BX & 2LIS_03_BF.
    Regards,
    Edited by: BhaminiJ on Aug 3, 2011 1:33 PM

  • Exchange Rate difference in Balance Sheet-Revaluation in Foreign Currency

    Hi
    I wanted more clarification on the Exchange rate difference the system calculates when we generate a balance sheet and revalue at a fixed rate. The system does not give a breakup of the echange rate calculated. How do we arrive at the exchange rate.
    And after having the exchange rate entries posted in the system. Can the system the show these values in the Balance sheet after Revaluation
    Regards
    Farheen

    Dear Gordan
    Below mentioned is  the balance sheet which is Revaluated in Euro(System Currency)at a Fixed Rate of 1.42.
    at the end of this report we can see that the system has calculated Exchange rate difference as Euro -66483.03 .We want a break up of that amount which is calculated by the system
    Account Name     Beginning of Year(EUR)     Current Period(EUR)     Beginning of Year(Revaluated by EUR)     Current Period(Revaluated by EUR)
    Asset                                          129,932.14        129,932.14                               115,984.30     115,984.30
    Fixed Assets                    
    Owned Assets                    
    Leasehold Improvements                    
    Computers                    
    Office Equipment                    
    Furniture And Fixtures                    
    Vehicles                    
    Medical Equipments                    
    Tangible Assets                    
    Capital Work-In-Progress                    
    Capital Work-In-Progress - Assets                    
    Investments     104,895.10     104,895.10                                 104,895.10 104,895.10
    Long Term Investments                    
    Short Term Investments     104,895.10     104,895.10     104,895.10     104,895.10
    Short term Investments                    
    Long Term Investments     104,895.10     104,895.10     104,895.10     104,895.10
    121001 - Equity Investment in Subsidiary-India     104,895.10     104,895.10     104,895.10     104,895.10
    Current Assets, Loans And Advances     25,037.04     25,037.04     11,089.20     11,089.20
    Current Assets     25,037.04     25,037.04     11,089.20     11,089.20
    Inventories                    
    Sundry Debtors                    
    Cash On Hand                    
    Bank Balances with Scheduled Banks In Current Accounts     25,037.04     25,037.04     11,089.20     11,089.20
    131401 - Marfin Popular Bank,Limassol,Cyprus-17911136139     9,935.51     9,935.51     9,935.51     9,935.51
    131402 - Marfin Popular Bank,Limassol,Cyprus-179132258722     13,940.48     13,940.48          
    131403 - Marfin Popular Bank,Limassol,Cyprus-179932258780     1,161.05     1,161.05     1,153.69     1,153.69
    Bank Balances with Scheduled Banks In Deposit Accounts                    
    Loans & Advances                    
    Loans to Subsidiary Companies                    
    Loans to Employees                    
    Advances Recoverable in Cash or for value to be received                    
    Advances recoverable in cash or in kind                    
    Prepaid Expenses                    
    Advances recoverable prvn.for Doubtdebts                    
    Deposits (General)                    
    Advance Tax/Tax Deducted at Source                    
    Pre-Launch Expenses (Deferred)                    
    Liability     206,065.33     206,065.33     182,467.33     182,467.33
    Loan Funds                    
    Secured Loans                    
    Term Loans From Bank                    
    Short Term Loan from Banks                    
    Vehicle Loans                    
    Interest Accured But Not Due                    
    Secured Loan from Companies                    
    Unsecured Loans                    
    Term Loans from Banks                    
    Unsecured loans From Companies                    
    Fixed Deposits                    
    Unsecured loans From Holding Company                    
    Unsecured loans From Subsidiaries                    
    Deferred Tax Liability                    
    Deferred Tax Liability                    
    Deferred Tax Liability                    
    Current Liabilities And Provision     206,065.33     206,065.33     182,467.33     182,467.33
    Current Liabilities     182,467.33     182,467.33     182,467.33     182,467.33
    Sundry Creditors     182,467.33     182,467.33     182,467.33     182,467.33
    231101 - Sundry Creditors - Supplier     182,467.33     182,467.33     182,467.33     182,467.33
    Advances From Customer                    
    Overdrawn Bank Balances                    
    Tax Deducted at Source                    
    Tax Deducted at Source - Non Resident u/s 195                    
    Other Taxes                    
    Other Liabilities - Statutory                    
    Other Liabilities - Salary Payables                    
    Provisions     23,598.00     23,598.00          
    Provision for Expenses     23,598.00     23,598.00          
    232106 - Provision for Expenses     23,598.00     23,598.00          
    Income Tax                    
    Accumulated Depreciation                    
    Leasehold Improvements                    
    Computers                    
    Office Equipments                    
    Furniture and Fixtures                    
    Vehicles                    
    Medical Equipments                    
    Software & their License                    
    Technical Knowhow                    
    Equity     -76,133.19     -76,133.19     -66,483.03     -66,483.03
    Shareholders' Funds     1,176.47     1,176.47          
    Share Capital     1,176.47     1,176.47          
    Authorized Share Capital                    
    Equity Share Capital                    
    Issued, Subscribed And Paid Up Share Capital     1,176.47     1,176.47          
    311201 - Equity Share Capital     1,176.47     1,176.47          
    Reserves And Surplus                    
    Share Premium Account                    
    Profit and Loss Account                    
    Profit Period     -77,309.66     -77,309.66          
    Exchange Rate Differences               -66,483.03     -66,483.03
    Edited by: Rekha Nagaraj on Dec 7, 2010 6:14 AM

  • Issue Finished Goods

    Hi All,
    For few finished goods we have not entered stock in our opening balance since we didnt ahev any stock for them.
    now the customer has returned some FG item which we have taken as sales return item. while trying to issue these items in the Bill of material of other items  we get an error " Item cost not found"
    wht could be the reason.

    Hi Prince......
    It seems you don't have put Item Cost while Entering Opening Stock.
    Please make sure of this. Else you may have to do inventory Revaluation of these Items......
    Regards,
    Rahul

  • Restricting issue of goods to cost center with respect to material type

    Dear Users,
    I have a requirement like we want to restrict issue of goods to cost center with respect to material type i.e., we want to issue goods to cost center only through reservation and that too only for specific material types. Is there any standard solution for this, please provide your suggestions.
    Thanks,
    Manoj

    Hi Ajay,
    Thanks for valuable input.
    I also thought in the same line , but user has the following concern on this:
    Assessment Cycle: As per Users, it cannot be used because this will allocate based on allocation basis. But they need, the values that was posted at the time of transaction and as per materials. So it wont be accurate through Assessment cycle,
    OKB9: They have different Cost center for different valuation area for the same GL Account.
    Hence through OKB9 also, we cannot post directly to COPA.
    That's the reason the above option were not adopted.
    My other concern to this is:
    In CKM3, we have two lines under consumption, one for Normal sales PGI and other is Cost Center.
    After doing revaluation of consumption in CKMLCP, we see one line under Cost Center :Revaluation of Consumption Figure"
    My question, where can I see that figure whether in any table or in Cost Center report??
    If that is also available we can try to match those values and post to COPA.
    Let me know your thought on this.
    Thanks and regards
    Kami

  • Goods issue/receipt print out

    Hi could any body let me know the print settings for goods issue & receipts and Logistics invoice verification.
    i tried with we01 for GRN , wa01 for GI, in nace settings but could not find the result.
    pls let me know the settings.especially for sub contract components issue print settings.
    regards
    Bheemasimha
    9900163939

    hi bheema,
    Configure Automatic Postings
    In this step, you enter the system settings for Inventory Management and Invoice Verification transactions for automatic postings to G/L accounts.
    You can then check your settings using a simulation function.
    Under Further information there is a list of transactions in Materials Management and their definitions.
    What are automatic postings?
    Postings are made to G/L accounts automatically in the case of Invoice Verification and Inventory Management transactions relevant to Financial and Cost Accounting.
    Example:
    Posting lines are created in the following accounts in the case of a goods issue for a cost center:
    Stock account
    Consumption account
    How does the system find the relevant accounts?
    When entering the goods movement, the user does not have to enter a G/L account, since the R/3 System automatically finds the accounts to which postings are to be made using the following data:
    Chart of accounts of the company code
    If the user enters a company code or a plant when entering a transaction, the R/3 System determines the chart of accounts which is valid for the company code.
    You must define the automatic account determination individually for each chart of accounts.
    Valuation grouping code of the valuation area
    If the automatic account determination within a chart of accounts is to run differently for certain company codes or plants (valuation areas), assign different valuation grouping codes to these valuation areas.
    You must define the automatic account determination individually for every valuation grouping code within a chart of accounts. It applies to all valuation areas which are assigned to this valuation grouping code.
    If the user enters a company code or a plant when entering a transaction, the system determines the valuation area and the valuation grouping code.
    Transaction/event key (internal processing key)
    Posting transactions are predefined for those inventory management and invoice verification transactions relevant to accounting. Posting records, which are generalized in the value string, are assigned to each relevant movement type in inventory management and each transaction in invoice verification. These contain keys for the relevant posting transaction (for example, inventory posting and consumption posting) instead of actual G/L account numbers.
    You do not have to define these transaction keys, they are determined automatically from the transaction (invoice verification) or the movement type (inventory management). All you have to do is assign the relevant G/L account to each posting transaction.
    Account grouping (only for offsetting entries, consignment liabilities, and price differences)
    Since the posting transaction "Offsetting entry for inventory posting" is used for different transactions (for example, goods issue, scrapping, physical inventory), which are assigned to different accounts (for example, consumption account, scrapping, expense/income from inventory differences), it is necessary to divide the posting transaction according to a further key: account grouping code.
    An account grouping is assigned to each movement type in inventory management which uses the posting transaction "Offsetting entry for inventory posting".
    Under the posting transaction "Offsetting entry for inventory posting", you must assign G/L accounts for every account grouping, that is, assign G/L accounts.
    If you wish to post price differences to different price difference accounts in the case of goods receipts for purchase orders, goods receipts for orders, or other movements, you can define different account grouping codes for the transaction key.
    Using the account grouping, you can also have different accounts for consignment liabilities and pipeline liabilities.
    Valuation class of material or (in case of split valuation) the valuation type
    The valuation class allows you to define automatic account determination that is dependent on the material. for example: you post a goods receipt of a raw material to a different stock account than if the goods receipt were for trading goods, even though the user enters the same transaction for both materials.
    You can achieve this by assigning different valuation classes to the materials and by assigning different G/L accounts to the posting transaction for every valuation class.
    If you do not want to differentiate according to valuation classes you do not have to maintain a valuation class for a transaction.
    Requirements
    Before you maintain automatic postings, you must obtain the following information:
    1. Valuation level (plant or company code)
    Establish whether the materials are valuated at plant or at company code level
    When valuation is at plant level, the valuation area corresponds to a plant.
    When valuation is at company code level, the valuation area corresponds to a company code.
    Define valuation level
    2. Chart of accounts and valuation grouping code per valuation area
    Find out whether the valuation grouping code is active.
    Activate split valuation
    If it is not active, determine the chart of accounts assigned to each valuation area (via the company code).
    If it is active, determine the chart of accounts and the valuation grouping code assigned to each valuation area.
    Group valuation areas
    You must define a separate account determination process for chart of accounts and each valuation grouping code.
    3. Valuation class per material type
    If you wish to differentiate the account determination process for specific transactions according to valuation classes, find out which valuation classes are possible for each material type.
    Define valuation classes
    4. Account grouping for offsetting entries to stock accounts
    Under
    Define account grouping for movement types , determine for which movement types an account grouping is defined for the transaction/event keys GGB (offsetting entry to stock posting), KON (consignment liabilities) and PRD (price differences).
    Default settings
    G/L account assignments for the charts of accounts INT and the valuation grouping code 0001 are SAP standard.
    Activities
    1. Create account keys for each chart of accounts and each valuation grouping code for the individual posting transactions. To do so, proceed as follows:
    a) Call up the activity
    Configure Automatic Postings .
    The R/3 system first checks whether the valuation areas are correctly maintained. If, for example, a plant is not assigned to a company code, a dialog box and an error message appear.
    From this box, choose Continue (next entry) to continue the check.
    Choose Cancel to end the check.
    The configuration menu Automatic postings appears.
    b) Choose Goto -> Account assignment.
    A list of posting transactions in Materials Management appears. For further details of the individual transactions, see Further information.
    The Account determination indicator shows whether automatic account determination is defined for a transaction.
    c) Choose a posting transaction.
    A box appears for the first posting transaction. Here you can enter a chart of accounts.
    You can enter the following data for each transaction:
    Rules for account number assignments
    With Goto -> Rules you can enter the factors on which the account number assignments depend:
    - debit/credit indicator
    - general grouping (= account grouping)
    - valuation grouping
    - valuation class
    Posting keys for the posting lines
    Normally you do not have to change the posting keys. If you wish to use new posting keys, you have to define them in the Customizing system of Financial Accounting.
    Account number assignments
    You must assign G/L accounts for each transaction/event key (except KBS). You can assign these accounts manually or copy them from another chart of accounts via Edit -> Copy .
    If you want to differentiate posting transactions (e.g. inventory postings) according to valuation classes, you must make an account assignment for each valuation class.
    Using the posting transaction "Offsetting entry for inventory posting", you have to make an account assignment for each account grouping
    If the transaction PRD (price differences) is also dependent on the account grouping, you must create three account assignments:
    - an account assignment without account grouping
    - an account assignment with account grouping PRF
    - an account assignment with account grouping PRA
    If the transaction KON (consignment and pipeline liabilities) is also dependent on the account grouping, you must create two account assignments:
    - an account assignment without account grouping (consignment)
    - an account assignment with account grouping (pipeline)
    d) Save your settings.
    2. Then check your settings with the simulation function.
    With the simulation function, you can simulate the following:
    Inventory Management transactions
    Invoice Verification transactions
    When you enter a material or valuation class, the R/3 system determines the G/L accounts which are assigned to the corresponding posting transactions. Depending on the configuration, the SAP system checks whether the G/L account exists
    In the simulation you can compare the field selection of the movement type with that of the individual accounts and make any corrections.
    If you want to print the simulation, choose Simulation -> Report.
    To carry out the simulation, proceed as follows:
    a) Choose Settings to check the simulation defaults for
    - the application area (Invoice Verification or Inventory Management)
    - the input mode (material or valuation class)
    - account assignment
    Instructions
    b) Choose Goto -> Simulation.
    The screen for entering simulation data appears.
    c) Depending on the valuation level, enter a plant or a company code on the screen.
    d) When you simulate Inventory Management transactions, goods movements are simulated. The R/3 system suggests the first movement type for simulation. If several movements are possible with this movement type, you can select a line.
    When you simulate Invoice Verification transactions, a list appears on the screen of the possible transaction types. Select a line.
    e) Then choose Goto -> Account assignments.
    A list appears of the posting lines which can be created by the selected transaction. For each posting line, the G/L account for the debit posting as well as the G/L account for the credit posting are displayed.
    f) From this screen, choose Goto -> Movement+ to get a list of the posting lines for the next movement type or transaction type.
    If you work with valuation classes, choose Goto -> Valuation class+ to receive the simulation for the next valuation class. This function is not possible when simulating with material numbers.
    Choose Goto -> Check screen layout to compare the movement type with the G/L accounts determined by the system and make any necessary corrections.
    Note
    The simulation function does NOT obviate the need for a trial posting!
    Further Notes
    The following list shows the individual transactions with examples of how they are used:
    AG1 - No documentation currently available.
    AG2 - No documentation currently available.
    AG3 - No documentation currently available.
    Expense/revenue from consumption of consignment material (AKO)
    This transaction is used in Inventory Management in the case of withdrawals from consignment stock or when consignment stock is transferred to own stock if the material is subject to standard price control and the consignment price differs from the standard price.
    Expenditure/income from transfer posting (AUM)
    This transaction is used for transfer postings from one material to another if the complete value of the issuing material cannot be posted to the value of the receiving material. This applies both to materials with standard price control and to materials with moving average price control. Price differences can arise for materials with moving average price if stock levels are negative and the stock value becomes unrealistic as a result of the posting. Transaction AUM can be used irrespective of whether the transfer posting involves a transfer between plants. The expenditure/income is added to the receiving material.
    Provisions for subsequent (end-of-period rebate) settlement (BO1)
    If you use the "subsequent settlement" function with regard to conditions (e.g. for period-end volume-based rebates), provisions for accrued income are set up when goods receipts are recorded against purchase orders if this is defined for the condition type.
    Income from subsequent settlement (BO2)
    The rebate income generated in the course of "subsequent settlement" (end-of-period rebate settlement) is posted via this transaction.
    Income from subsequent settlement after actual settlement (BO3)
    If a goods receipt occurs after settlement accounting has been effected for a rebate arrangement, no further provisions for accrued rebate income can be managed by the "subsequent settlement" facility. No postings should be made to the account normally used for such provisions. As an alternative, you can use this transaction to post provisions for accrued rebate income to a separate account in cases such as the one described.
    Supplementary entry for stock (BSD)
    This account is posted when closing entries are made for a cumulation run. This account is a supplementary account to the stock account; that is, the stock account is added to it to determine the stock value that was calculated via the cumulation. In the process, the various valuation areas (for example, commercial, tax), that are used in the balance sheet are taxed separately.
    Change in stock (BSV)
    Changes in stocks are posted in Inventory Management at the time goods receipts are recorded or subsequent adjustments made with regard to subcontract orders.
    If the account assigned here is defined as a cost element, you must specify a preliminary account assignment for the account in the table of automatic account assignment specification (Customizing for Controlling) in order to be able to post goods receipts against subcontract orders. In the standard system, cost center SC-1 is defined for this purpose.
    Stock posting (BSX)
    This transaction is used for all postings to stock accounts. Such postings are effected, for example:
    In inventory management in the case of goods receipts to own stock and goods issues from own stock
    In invoice verification, if price differences occur in connection with incoming invoices for materials valuated at moving average price and there is adequate stock coverage
    In order settlement, if the order is assigned to a material with moving average price and the actual costs at the time of settlement vary from the actual costs at the time of goods receipt
    Because this transaction is dependent on the valuation class, it is possible to manage materials with different valuation classes in separate stock accounts.
    @1A@Caution
    Take care to ensure that:
    A stock account is not used for any transaction other than BSX
    Postings are not made to the account manually
    The account is not changed in the productive system before all stock has been booked out of it
    Otherwise differences would arise between the total stock value of the material master records and the balance on the stock account.
    Revaluation of "other" consumptions (COC)
    This transaction/event key is only relevant to Brazil. It is used if a revaluation report is used for company codes in Brazil.
    The revaluation report uses the actual prices determined by the material ledger/actual costing to:
    Revaluate costs on the basis of actual prices
    Post the price differences arising from "other" consumptions (e.g. consumption to cost center) to a collective account
    This transaction/event key is needed to post the price differences. The account specified here is posted with the price differences for "other" consumptions.
    No documentation currently available.
    Small differences, Materials Management (DIF)
    This transaction is used in Invoice Verification if you define a tolerance for minor differences and the balance of an invoice does not exceed the tolerance.
    Purchase account(EIN), purchase offsetting account (EKG), freight purchase account (FRE)
    These transactions are used only if
    Purchase Account Management is active in the company code.
    Note
    Due to special legal requirements, this function was developed specially for certain countries (Belgium, Spain, Portugal, France, Italy, and Finland).
    Before you use this function, check whether you need to use it in your country.
    Freight clearing (FR1), provision for freight charges (FR2), customs duty clearing (FR3), provision for customs duty (FR4)
    These transactions are used to post delivery costs (incidental procurement costs) in the case of goods receipts against purchase orders and incoming invoices. Which transaction is used for which delivery costs depends on the condition types defined in the purchase order.
    You can also enter your own transactions for delivery costs in condition types.
    External service (FRL)
    The transaction is used for goods and invoice receipts in connection with subcontract orders.
    If the account assigned here is defined as a cost element, you must specify a preliminary account assignment for the account in the table of automatic account assignment specification (Customizing for Controlling) in order to be able to post goods receipts against subcontract orders. In the standard system, cost center SC-1 is defined for this purpose.
    External service, delivery costs (FRN)
    This transaction is used for delivery costs (incidental costs of procurement) in connection with subcontract orders.
    If the account assigned here is defined as a cost element, you must specify a preliminary account assignment for the account in the table of automatic account assignment specification (Customizing for Controlling) in order to be able to post goods receipts against subcontract orders. In the standard system, cost center SC-1 is defined for this purpose.
    Offsetting entry for stock posting (GBB)
    Offsetting entries for stock postings are used in Inventory Management. They are dependent on the account grouping to which each movement type is assigned. The following account groupings are defined in the standard system:
    AUA: for order settlement
    AUF: for goods receipts for orders (without account assignment)
    and for order settlement if AUA is not maintained
    AUI: Subsequent adjustment of actual price from cost center directly
    to material (with account assignment)
    BSA: for initial entry of stock balances
    INV: for expenditure/income from inventory differences
    VAX: for goods issues for sales orders without
    account assignment object (the account is not a cost element)
    VAY: for goods issues for sales orders with
    account assignment object (account is a cost element)
    VBO: for consumption from stock of material provided to vendor
    VBR: for internal goods issues (for example, for cost center)
    VKA: for sales order account assignment
    (for example, for individual purchase order)
    VKP: for project account assignment (for example, for individual PO)
    VNG: for scrapping/destruction
    VQP: for sample withdrawals without account assignment
    VQY: for sample withdrawals with account assignment
    ZOB: for goods receipts without purchase orders (mvt type 501)
    ZOF: for goods receipts without production orders
    (mvt types 521 and 531)
    You can also define your own account groupings. If you intend to post goods issues for cost centers (mvt type 201) and goods issues for orders (mvt type 261) to separate consumption accounts, you can assign the account grouping ZZZ to movement type 201 and account grouping YYY to movement type 261.
    @1A@Caution
    If you use goods receipts without a purchase order in your system (movement type 501), you have to check to which accounts the account groupings are assigned ZOB
    If you expect invoices for the goods receipts, and these invoices can only be posted in Accounting, you can enter a clearing account (similar to a GR/IR clearing account though without open item management), which is cleared in Accounting when you post the vendor invoice.
    Note that the goods movement is valuated with the valuation price of the material if no external amount has been entered.
    As no account assignment has been entered in the standard system, the assigned account is not defined as a cost element. If you assign a cost element, you have to enter an account assignment via the field selection or maintain an automatic account assignment for the cost element.
    Purchase order with account assignment (KBS)
    You cannot assign this transaction/event key to an account. It means that the account assignment is adopted from the purchase order and is used for the purpose of determining the posting keys for the goods receipt.
    Exchange rate differences in the case of open items (KDM)
    Exchange rate differences in the case of open items arise when an invoice relating to a purchase order is posted with a different exchange rate to that of the goods receipt and the material cannot be debited or credited due to standard price control or stock undercoverage/shortage.
    Differences due to exchange rate rounding, Materials Management (KDR)
    An exchange rate rounding difference can arise in the case of an invoice made out in a foreign currency. If a difference arises when the posting lines are translated into local currency (as a result of rounding), the system automatically generates a posting line for this rounding difference.
    KDV - No documentation currently available.
    Consignment liabilities (KON)
    Consignment liabilities arise in the case of withdrawals from consignment stock or from a pipeline or when consignment stock is transferred to own stock.
    Depending on the settings for the posting rules for the transaction/event key KON, it is possible to work with or without account modification. If you work with account modification, the following modifications are available in the standard system:
    None for consignment liabilities
    PIP for pipeline liabilities
    Offsetting entry for price differences in cost object hierarchies (KTR)
    The contra entry for price difference postings (transaction PRK) arising through settlement via material account determination is carried out with transaction KTR.
    LKW - No documentation currently available.
    Price differences (PRD)
    Price differences arise for materials valuated at standard price in the case of all movements and invoices with a value that differs from the standard price. Examples: goods receipts against purchase orders (if the PO price differs from the standard pricedardpreis), goods issues in respect of which an external amount is entered, invoices (if the invoice price differs from the PO price and the standard price).
    Price differences can also arise in the case of materials with moving average price if there is not enough stock to cover the invoiced quantity. In the case of goods movements in the negative range, the moving average price is not changed. Instead, any price differences arising are posted to a price difference account.
    Depending on the settings for the posting rules for transaction/event key PRD, it is possible to work with or without account modification. If you use account modification, the following modifications are available in the standard system:
    None for goods and invoice receipts against purchase orders
    PRF for goods receipts against production orders and
    order settlement
    PRA for goods issues and other movements
    PRU for transfer postings (price differences in the case
    of external amounts)
    PRK - No documentation currently available.
    PRP - No documentation currently available.
    PRQ - No documentation currently available.
    PRV - No documentation currently available.
    PRY - No documentation currently available.
    RAP - No documentation currently available.
    RKA - No documentation currently available.
    Provision for delivery costs (RUE)
    Provisions are created for accrued delivery costs if a condition type for provisions is entered in the purchase order. They must be cleared manually at the time of invoice verification.
    Taxes in case of transfer posting GI/GR (TXO)
    This transaction/event key is only relevant to Brazil (nota fiscal).
    Revenue/expense from revaluation (UMB)
    This transaction/event key is used both in Inventory Management and in Invoice Verification if the standard price of a material has been changed and a movement or an invoice is posted to the previous period (at the previous price).
    Expenditure/income from revaluation (UMD)
    This account is the offsetting account for the BSD account. It is posted during the closing entries for the cumulation run of the material ledger and has to be defined for the same valuation areas.
    Unplanned delivery costs (UPF)
    Unplanned delivery costs are delivery costs (incidental procurement costs) that were not planned in a purchase order (e.g. freight, customs duty). In the SAP posting transaction in Logistics Invoice Verification, instead of distributing these unplanned delivery costs among all invoice items as hitherto, you have the option of posting them to a special account. A separate tax code can be used for this account.
    Input tax, Purchasing (VST)
    Transaction/event key for tax account determination within the "subsequent settlement" facility for debit-side settlement types. The key is needed in the settlement schema for tax conditions.
    Goods issue, revaluation (inflation) (WGI)
    This transaction/event key is used if already-posted goods issues have to be revaluated following the determination of a new market price within the framework of inflation handling.
    Goods receipt, revaluation (inflation) (WGR)
    This transaction/event key is used if already-effected transfer postings have to be revaluated following the determination of a new market price within the framework of inflation handling. This transaction is used for the receiving plant, whereas transaction WGI (goods receipt, revaluation (inflation)) is used for the plant at which the goods are issued.
    GR/IR clearing (WRX)
    Postings to the GR/IR clearing account occur in the case of goods and invoice receipts against purchase orders. For more on the GR/IR clearing account, refer to the SAP Library (documentation MM Material Valuation).
    Caution
    You must set the Balances in local currency only indicator for the GR/IR clearing account to enable the open items to be cleared. For more on this topic, see the field documentation.
    see the below link also
    http://209.85.175.104/search?q=cache:7FJheuTAxiQJ:help.sap.com/bp_afsv1500/CP_AFS_DE/documentation/AFS_Solution_Scope_EN_DE.docprintsettingsforgoodsissue%26receiptsandLogisticsinvoice+verification.&hl=en&ct=clnk&cd=2
    thanks
    saGAR
    REWARD ME IF USEFULL

Maybe you are looking for