Split Account posting

Hello Experts,
can we do positngs in split account (i.e. in multiple accounts) like we are having sales tax posting account and sales tax is 16%, in this 16 % >> 15% is sales tax and 1% is excise duty.
So we need to split the posting in two accounts:
1. in Sales Tax account
2. in Excise Duty
I am using UDF's in AR invoice and have got amounts split in two values i.e. 15% and 1%.
Kindly Help,

Have a look at 'Tax Type Combination' of 'BED+VAT' tax code in the 'OEC Computers India' demo database from SAP.
Here they would have configured the 'BED+VAT' with following combination:
BED 16%
Cess 1%
VAT 4%.
Replicate the same for your requirement

Similar Messages

EDI - Outbound Accounting Posting Journals to External System

Hi Experts,
I have a requirement in which I have to outbound
Accouting Journals to an external system...
Does standard SAP support such a functionality.
I looked at the outbound process code and was unable
to find anything on accounting. (which does make sense...) I also noticed that journal entry transactions such as FB01 do not have output controls like SD or MM.
Would I not be able to utilize standard idocs in this case?

Hi Rolmega,
Please refer the OSS note 616804 .That is exactly matching your requirement and guide you through out the development.
OSS note 616804.
Create a BAPI which can be used to create cash journal documents.
To do this, carry out the steps specified below in your system, or import the relevant Support Package.
1. In Transaction SE37, select the menu option 'Goto' -> 'Function Groups' -> 'Create group'. Create function group SAPLFCJ_BAPI with the short text 'BAPI for FI cash journal' and save it.
2. In Transaction SE37, create function module BAPI_CASHJOURNALDOC_CREATE in function group SAPLFCJ_BAPI in package CAJO with the short text 'Save FI cash journal documents' as a remote-enabled module.
a) Create the following function module documentation for the function module:
                        With BAPI BAPI_CASHJOURNALDOC_CREATE, you can save a document when you execute in the FI cash journal, in the same way as when you make an entry via the Interface Transaction FBCJ.
                        If the TESTRUN field is set, the system only carries out the checks and not the actual backup process when the database is updated.
                        If you want to save a cash journal document, the program that calls the BAPI has to execute the COMMIT WORK to update the document.
                        A document can contain several split rows.
                        You can post either expenses or receipts for each document. In other words, either the ITEMS-P_PAYMENTS or the ITEMS-P_RECEIPTS field has to be filled in all line items.
                        If the document contains several line items or entries in the control table, assigned net or tax base amounts are deleted.
                        The initiator has to assign the item number (ITEMS-POSITION_NUMBER) for all line items or for none.
                        If the initiator assigns one-time data, the item numbers (CPD_ITEMS-POSITION_NUMBER) have to correspond to the respective line item (ITEMS-POSITION_NUMBER). The same item number may be used in one one-time line item only.
                        If the extended withholding tax is active in the company code used, you can create only one line item and no split document for vendors or customers that are relevant for withholding tax.
                        The vendor has to be filled for all assigned rows of the withholding tax information (table WTAX_ITEMS).
                        If withholding tax information is to be assigned, the indicator for withholding tax type (WTAX_ITEMS-WTAXTYPE) has to be filled with a value that is defined in the vendor master record. In addition, the same indicator for the withholding tax type may be assigned in one line of the ITEMS table only. The system does not take into account the external item number for withholding tax information.
                        In the TAX_ITEMS table, the same tax code may be assigned in only one line.
                        If there are entries in the TAX_ITEMS table, every tax code or jurisdiction code of this table has to be assigned in at least one line of the ITEMS table or be able to be derived from the Customizing for the business transaction.
                        If, in Customizing, there are accounts and tax codes for interface transactions that are flagged as not ready for input, then the BAPI derives values that are transferred in the ITEMS table again and overwrites them if necessary.
                        A check recognizes that field HEADER-CHECK_NUMBER is filled when the BAPI is called.
                        You cannot use the BAPI to save a document in a cash journal if this cash journal is simultaneously blocked by another interface user or another BAPI initiator. When you execute the BAPI, the system also sets a block for other users.
                        The initiator of the BAPI can transfer additional field values via the EXTENSION_IN table and can process them further in a BADI called in the customer_function subroutine.
                        You cannot change saved documents or deposit checks.
a) Enter the following import parameters:
Parameter Name Type Associated Type Opt Pass Value Short text
HEADER          LIKE   BAPI_CJ_HEADER        X           Document header
Long text:
In the HEADER structure, you can assign the document header information of the cash journal document to be saved. Basically, the structure corresponds to the fields of the TCJ_DOCUMENTS table that are ready for input on the cash journal interface and which contain header information only.
TESTRUN         LIKE BAPI2021_HELP    X    X     Indicator for test run
                        TESTRUN                     without update
Long text:
If the TESTRUN field is set, the external structures transferred when the BAPI is called are assigned to the internal cash journal structures. The relevant checks are also carried out. However, no update occurs to save the document on the database.
b) Enter the following export parameters:
Parameter Name Type Associated Type Pass Value Short text
COMPANY_CODE    LIKE BAPI_CJ_HEADER   X          Company code
                        -COMP_CODE
Long text:
The COMPANY_CODE parameter contains the company code of the saved cash journal document.
CASH_JOURNAL_NUMBER LIKE BAPI_CJ_HEADER       Cash journal number
                          -CAJO_NUBMER
Long text:
The CASH_JOURNAL_NUMBER parameter contains the cash journal of the saved cash journal document.
FISCAL_YEAR         LIKE BAPI_CJ_KEY   X     Fiscal year
                          -FISC_YEAR
Long text:
The FISCAL_YEAR parameter contains the fiscal year of the saved cash journal document, but it is only filled for check totals documents.
CASH_JOURNAL_DOC_NO LIKE BAPI_CJ_KEY   X     Document number
                          -POSTING_NUMBER     cash journal document
Long text:
The CASH_JOURNAL_DOC_NO parameter contains the internal document number of the saved cash journal document.
c) Enter the following table parameters:
Parameter Name Type Associated Type Optional Short text
ITEMS           LIKE BAPI_CJ_ITEMS            Cash journal documentitems
Long text:
In the ITEMS table, you can assign the information for the line items of the cash journal document to be saved. Basically, the spaces in the table fields correspond to the fields of the TCJ_POSITIONS table that are ready for input on the cash journal interface and which contain item information only. You can assign several line items per document, in the same way as for the split lines that can be entered via the interface transaction.
TAX_ITMES     LIKE BAPI_CJ_TAX_ITEMS X      Cash journal tax items
Long text:
In the TAX_ITEMS table, you can assign tax information for the cash journal document to be saved. In this way, you can for example affect tax amounts derived from the system, in the same way as tax information is changed on the split window of the interface transaction.
CPD_ITEMS     LIKE BAPI_CJ_CPD_ITEMS X      One-time data
Long text:
In the CPD_ITEMS table, you can assign information for one-time customers or vendors that are contained in line items of the ITEMS table. Basically, the table fields correspond to the fields of the TCJ_CPD table, which are ready for input on the one-time window.
WTAX_ITEMS    LIKE BAPI_CJ_WTAX_ITEMS X      Withholding tax in the
                                                cash journal document
Long text:
In the WTAX_ITEMS table, you can assign information on the extended withholding tax for a vendor that is contained in a line item of the CJ_ITEMS table. Basically, the table fields correspond to the fields of the TCJ_WTAX_ITEMS table, which can be changed the withholding tax window.
EXTENSION_IN LIKE BAPIPAREX          X   Container for
                                             'Customer Exit'
Long text:
In the EXTENSION_IN parameter, you can transfer parameters that can be processed further in the BADI CJ_DOCUMENT, which the user of the BAPI BAPI_CASH_JOURNAL_CREATE has to implement.
For example, you can assign data to the TCJ_POSITIONS table in the form of Include CI_COBL or information profitability segments or real estate.
RETURN         LIKE BAPIRET2               Return parameter
Long text:
In Table RETURN, the messages of the program are returned to the initiator of the BAPI.
d) Save and activate the changes.
1. Using Transaction SE11, create data type (structure) BAPI_CJ_HEADER in Package CAJO with the short description 'Cash journal document header for transfer to a BAPI'.
a) Via the 'Extras' menu option, select 'Cannot Be Enhanced' as the enhancement category.
b) Create the following fields:
Field            Data element
COMP_CODE        BUKRS
CAJO_NUMBER      CJNR
CURRENCY         WAERS
CURRENCY_ISO     WAERS_ISO
DOC_DATE         BLDAT
PSTNG_DATE       BUDAT
REF_DOC_NO       XBLNR1
BP_NAME          CJBPNAME
ALLOC_NMBR       DZUONR
TEXT1            CJDOCTEXT100
TEXT2            CJDOCTEXT30
CHECK_NUMBER     SCKNR_EB
CHECK_ISSUER     CJCHECKISSUER
BANK_KEY         BANKK
BANK_ACCT        BANKN
BANK_CTRY        BANKS
BANK_CTRY        BANKS
BANK_CTRY_ISO    BANKS_ISO
SCBANK_IND       LZBKZ
SUPCOUNTRY       LANDL
SUPCOUNTRY_ISO   LANDL_ISO
c) Save and activate the changes.
2. In Transaction SE11, create data type (structure) BAPI_CJ_ITEMS in Package CAJO with the short description 'Cash journal line item for transfer to a BAPI'.
a) Via the 'Extras' menu option, select 'Cannot Be Enhanced' as enhancement category.
b) Create the following fields:
Field            Data element
POSITION_NUMBER CJBUZEI
TRANSACT_NUMBER CJTRANSNUMB
P_RECEIPTS       BAPIWRBTR
P_PAYMENTS       BAPIWRBTR
P_NET_AMOUNT     BAPIWRBTR
H_NET_PAYMENT_WT BAPIWRBTR
GL_ACCOUNT       HKONT
TAX_CODE         MWSKZ
TAXJURCODE       TXJCD
VENDOR_NO        LIFNR
CUSTOMER         KUNNR
POSITION_TEXT    CJPOSTEXT
BUS_AREA         GSBER
TR_PART_BA       PARGB
TRADE_ID         RASSC
CS_TRANS_T       RMVCT
FUNC_AREA        FKBER
CO_AREA          KOKRS
COSTCENTER       KOSTL
ACTTYPE          LSTAR
ORDERID          AUFNR
ORDER_ITNO       CO_POSNR
CALC_MOTIVE      BEMOT
COSTOBJECT       KSTRG
CO_BUSPROC       CO_PRZNR
PROFIT_CTR       PRCTR
PART_PRCTR       PPRCTR
WBS_ELEM         PS_POSID
NETWORK          NPLNR
ACTIVITY         VORNR
ASSETMAINO       BF_ANLN1
ASSETSUBNO       BF_ANLN2
VALUEDATE        BF_BZDAT
ASSETTRTYP       BF_ANBWA
PLANT            WERKS_D
VAL_TYPE         BWTAR_D
MATERIAL         MATNR
SALES_ORD        KDAUF
SCHED_LINE       KDEIN
S_ORD_ITEM       KDPOS
FM_AREA          FIKRS
FUNDS_CTR        FISTL
CMMT_ITEM        FIPOS
FUND             BP_GEBER
FUNDS_RES        KBLNR_FI
RES_ITEM         KBLPOS
PERSON_NO        PERNR_D
BUPLA            BUPLA
SECCO            SECCO
c) Save and activate the changes.
3. In Transaction SE11, create the data type (structure) BAPI_CJ_TAX_ITEMS in Package CAJO with the short description 'One-time data of cash journal line items for transfer to a BAPI'.
a) Via the 'Extras' menu option, select 'Cannot Be Enhanced' as the enhancement category.
b) Create the following fields:
Field            Data element
TAX_CODE         MWSKZ
AMT_TAX          BAPITXBTR
AMT_BASE         BAPIFWBAS
TAXJURCODE       TXJCD
c) Save and activate the changes.
4. In Transaction SE11, create the data type (structure) BAPI_CJ_CPD_ITEMS in Package CAJO with the short description 'One-time data of cash journal line items for transfer to a BAPI'.
a) Via the 'Extras' menu option, select 'Cannot Be Enhanced' as the enhancement category
b) Create the following fields:
Field            Data element
POSITION_NUMBER CJBUZEI
ANRED            ANRED
NAME             NAME1_GP
NAME_2           NAME2_GP
NAME_3           NAME3_GP
NAME_4           NAME4_GP
SOLE_PROP        STKZN
REP_NAME         REPRES
STREET           STRAS_GP
POSTL_CODE       PSTLZ
CITY             ORT01_GP
COUNTRY          LAND1_GP
COUNTRY_ISO      LAND1_ISO
PO_BOX           PFACH
POBX_PCD         PSTL2
REGION           REGIO
POBK_CURAC       PSKTO
BANK_ACCT        BANKN
BANK_NO          BANKL
BANK_CTRY        BANKS
BANK_CTRY_ISO    BANKS_ISO
CTRL_KEY         BKONT
BANK_REF         BKREF
INSTR_KEY        DTAWS
DME_IND          DTAMS
TAX_NO_1         STCD1
TAX_NO_2         STCD2
TAX_NO_3         STCD3
TAX_NO_4         STCD4
SLS_PUR_TX       STKZU
FITYP            J_1AFITP_D
TAX_NO_TY        J_1ATOID
EQUAL_TAX        STKZA
SPRAS            CHAR_LG_01
LANGU_ISO        LAISO
BUS_TYPE         GESTYP
IND_TYPE         INDTYP
c) Save and activate your changes.
5. In Transaction SE11, create the data type (structure) BAPI_CJ_WTAX_ITEMS in Package CAJO with the short description 'Withholding tax in cash journal document for transfer to a BAPI'.
a) Via the 'Extras' menu option, select 'Cannot Be Enhanced' as the enhancement category.
b) Create the following fields:
Field            Data element
POSITION_NUMBER CJBUZEI
VENDOR_NO        LIFNR
WTAXTYPE         WITHT
WT_WITHCD        WT_WITHCD
W_TAX_BASE       BAPIQSSHB
WI_TAX_AMT       BAPIQBSHB
c) Save and activate the changes.
6. In Transaction SE11, create the data type (structure) BAPI_CJ_KEY in Package CAJO with the short description 'Key fields for cash journal documents'.
a) Via the 'Extras' menu option, select 'Cannot Be Enhanced' as the enhancement category.
b) Create the following fields:
Field            Data element
FISC_YEAR        GJAHR
POSTING_NUMBER   CJBELNR
c) Save and activate the changes.
7. Using Transaction SE91, create the following messages for message class FCJ and select the 'Self-explanatory' field for each one:
a) 011: 'Document & & & was saved successfully.'
b) 012: 'Enter a gross amount.'
c) 013: 'Enter only the disbursement or incoming payment amount for each document.
d) 014: 'Enter the item numbers for all items or for none of them.'
e) 015: 'The number of tax items may not be larger than the number of items.'
f) 016: 'Only one tax item allowed per tax code/jurisdiction code.'
g) 017: 'Enter the item number for one-time items.'
h) 018: 'With several line items (split), do not enter any withholding tax items.'
i) 019: 'Business transaction without G/L account or tax code.'
j) 020: 'No line item with tax code/jurisdiction code of the tax item.'
k) 021: 'In company code & taxes without jurisdiction code.'
l) 022: 'Do not enter any tax item for posting indicator '3' (T007B-STBKZ)'
m) 023: 'Document could not be saved. Correct the errors listed'
n) 024: 'Business place + section code only with extended withholding tax.
o) 025: 'Net/tax base is deleted for several items or tax items'
p) 026: 'No line item corresponds to one-time item &.'
q) 027: 'Do not enter any withholding tax info if customer not w.tax-relevant'
r) 028: 'Do not enter any withholding tax info if vendor not w.tax-relevant'
s) 029: 'Do not enter any withholding tax info for G/L account posting.'
t) 030: 'Vendor in withholding tax information is not in line item.'
u) 031: 'Only one one-time item is allowed per item number.'
v) 032: 'Only one withholding tax item is allowed per withholding tax type.'
w) 033: 'Number of assigned withholding tax items deviates from master data.'
x) 034: 'No vendor required for business transaction.
y) 035: 'No customer required for business transaction.'
z) 036: 'Enter only receipts for checks.'
8. In Transaction SE37, call the FCJ_SAVE and FCJ_SAVE_DOCUMENT function modules in change mode.
a) Add import parameter I_XBAPI of TYPE BOOLEAN to these function modules. Select the Optional and Pass Value fields and enter the short text 'Indicator whether the call occurs from a BAPI'.
b) Also add the import parameters I_POSTING_NUMBER, LIKE, ISCJ_POSTINGS-POSTING_NUMBER for the function module FCJ_SAVE_DOCUMENT. Select the Optional and Pass Value fields.
c) Save and activate the changes.
9. In Transaction SE37, create the function module FCJ_SAVE_DOCUMENT_BALANCE_BAPI in the function group SAPLFCJ_PROCESS_MANAGER in Package CAJO with the short text 'Save cash journal document and balances for BAPI' as an update module with 'Start immed'.
a) Enter the following import parameters:
Parameter Name      Type Associated Type           Opt Pass Value
I_COMP_CODE         LIKE TCJ_C_JOURNALS-COMP_CODE       X
I_CAJO_NUMBER       LIKE TCJ_C_JOURNALS-CAJO_NUMBER     X
I_CURRENCY           LIKE TCJ_DOCUMENTS-CURRENCY         X
I_TYP               TYPE   CJTRANSTYP                     X
I_DISPLAY_PERIOD_LO LIKE SY-DATUM                        X
I_DISPLAY_PERIOD_HI LIKE SY-DATUM                        X
I_POSTING           LIKE    ISCJ_POSTINGS                  X
I_POSTING_NUMBER    LIKE ISCJ_POSTINGS-POSTING_NUMBER   X
b) Enter the following tables:
Parameter Name      Type Associated Type
ITCJ_POSTINGS       LIKE ISCJ_POSTINGS
ITCJ_WTAX_ITEMS     LIKE TCJ_WTAX_ITEMS
ITCJ_SPLIT_POSTINGS LIKE ISCJ_POSTINGS
ITCJ_CPD            LIKE TCJ_CPD
10. In Transaction SE18, define the BADI CJ_DOCUMENT. The corresponding interface is IF_EX_CJ_DOCUMENT.
               The method has the following 'Changing' parameter: Parameter             Type        Associated Type
C_ITCJ_SPLIT_POSTINGS Type        ISCJ_POSTINGS
C_ITCJ_SPLIT_TAXES    Type        ISCJ_POSTINGS
C_ITCJ_CPD              Type        TCJ_CPD
C_ITCJ_WTAX_ITEMS     Type        TCJ_WTAX_ITEMS
C_EXTENSION2           Type        BAPIPAREX
C_RETURN                Type        BAPIRET2
              You can use an implementation of this BADI to change the cash journal structures before the data check is processed.
1. Implement the attached corrections in your system.
2. In Transaction SE37, release the function module BAPI_CASHJORUNAL_DOC_CREATE via the menu path 'Function module' -> 'Release' -> 'Release'.
3. In Transaction SWO1, create the object type BUS2023.
a) Create the following key fields for the object type:
Key field           Name               Data type reference
CompanyCode       Company Code        TCJ_DOCUMENTS
                                        -COMP_CODE
CashJournalNumber Cash Journal Number TCJ_DOCUMENTS
                                        -CAJO_NUMBER
FiscalYear        Fiscal Year         TCJ_DOCUMENTS
                                        -FISC_YEAR
CashJournalDocNo Cash Journal        TCJ_DOCUMENTS
                  Document Number     -POSTING_NUMBER
b) Create the 'Create' method synchronously and instance-independent as an 'API function' with the name BAPI_CASHJOURNALDOC_CREATE.
                        Create the following parameters for the method: Parameter          Obj Type Imp. Man. Exp.
Header             BUS2023    X     X
Testrun            BUS2023    X
CompanyCode          BUS2023                X
CashJournalNumber   BUS2023                X
FiscalYear         BUS2023                X
CashJournalDocNo   BUS2023                X
Items               BUS2023    X     X
TaxItems           BUS2023    X
CPDItems           BUS2023    X
WTaxItems          BUS2023    X
ExtensionIn        BUS2023    X
Return             BUS2023                X
a) Create the 'ExistenceCheck' method synchronously and define the following source code:
                        begin_method existencecheck changing container.
                        DATA: l_mandt TYPE sy-mandt.
                        SELECT SINGLE mandt INTO l_mandt
                        FROM tcj_documents
                         WHERE comp_code = object-key-companycode
                           AND cajo_number = object-key-cashjournalnumber
                           AND fisc_year = space
                           AND posting_number = object-key-cashjournaldocno.
                        check sy-subrc <> 0.
                        exit_object_not_found.
                        end_method.
a) Under the menu option 'Goto' -> 'Documentation', define the following text for object type BUS2023:
                        A cash journal document is assigned to a cash journal and a company code.
                        It contains a unique document number from a company code-dependent number range interval that is independent of the number range interval of the G/L document. Cash journal documents are also numbered sequentially per company code and cash journal.
                        A cash journal document contains the offsetting entries for the G/L account of the cash journal in which G/L or person accounts are posted to for the business transaction.
                        You can save, delete, post or reverse a cash journal document. In the two last cases, there is a corresponding G/L document. This can be a receipt, a disbursement of cash, or the receipt of checks.
1. In Transaction BDBG, set up the IDOC processing for the object type BUS2023 and the method CREATE.
               The function module for ALE outbound processing with data refining is ALE_CASHJOURNALDOC_CREATE.
               The function module for ALE inbound processing is called IDOC_INPUT_CAJODOC_CREATE.
1. In Transaction 'SALE', maintain the ALE distribution. Here, maintain the steps generally required for a distribution process. Take into account the existing documentation of the operation. Execute the following steps for the BAPI used to save cash journal documents.
a) Maintain the distribution model under the path 'Model and Implement Business Processes' -> 'Maintain Distribution Model and Distribute Views'. The object name is 'CashJournalDoc' and the method name is 'Create'.
b) Execute the menu option 'Edit' -> 'Model view' -> 'Distribute' for the selected model view.
c) Select the path 'Model and Implement Business Processes' -> 'Partner Profiles and Time of Processing' -> 'Generate Partner Profiles'. (See corresponding documentation in document OALE_AUTOPARTN_BD82.) Enter the selected model view in the distribution model and the selected target system as the partner system.
2. To monitor the distribution of the IDOCs, use Transaction BD87 in both the sender system and the receiver system, and you can reach it via the path 'Tools' -> 'ALE' -> 'ALE Administration' -> 'Monitor' -> 'Status Monitor'. The relevant message type is CASHJOURNALDOC_CREATE.

Header price into revenue account posting

Hello,
We have a condition type with calculation type is set as FIXED VALUE and relevant for header condition. When we insert the price in document header for header condition type, system automatically replicates/split the price into line item wise and during revenue account postings, system post the value for each line item instead the header price, example - PRICE IN BILLING DOCUMENT
Header Price: Stamp Value: 100 USD
Line Itme 1:
Quantity: 1
Basic Price : 200
Stamp Value : 50
Line Item 2:
Quantity: 1
Basic Price : 200
Stamp Value : 50
Revenue Account Posting -
Customer 500 Dr
Revenue Line 1: 200 Cr
Stamp value: 50 Cr
Revenue Line 2: 200 Cr
Stamp Value: 50 Cr
However we need the value in revenue account posting as below -
Customer 500 Dr
Stamp value: 100 Cr
Revenue Line 1: 200 Cr
Revenue Line 2: 200 Cr
Please suggest
Best Regards,
Goutham

Hello Goutham,
if I understood well your requirement:
2 billing items with 2 materials, every item has Price condition and Stamp value condition.
You want in FI document the 2 Price conditions separated, creating 2 FI lines.
Whilst the 2 Stamp conditions joined in 1 FI line.
In the standard, SD passes to FI one line for every condition of every item (+ customer line).
Then in FI side the lines are summairzed, or not, depending on setting in OBCY.
If in OBCY there is only the line '' '' then system does not summarize the lines with different materials.
So in the standard there is not a solution for your requirement (as both Price line and Stamp value line have material).
The lonely possibility is to clear the material in the lines referred to Stamp value condition, and leave the material in the others.
In this way only the Stamp value lines will be summarized.
This can be done by one of userexits mentioned in note [301077|https://bosap-support.wdf.sap.corp/sap/support/notes/301077].
Consider theis would be a modification, and so it is not supported by SAP.
Best regards,
Ivano.

Revenue account posting

Dear All
I have one scenario Please check and please suggest.
Condition type                         Value     Account Key     Tax Code
PR00 BASIC PRICE                    1000
ZRP1     30% OF PR00          300               ERL
ZVAT     0 ON ZPR1             0              MW3                  A0
ZPR2     70% of PR00            700               ERL
VAT     8% ON ZPR2                 56               MW3                 AR
now posting is done 3000GL account with value 1000 and tax code A0
But I want posting in account should be like this
in revenue account in following ways :
gl code
30000     300 with A0 tax code
30000     700 with AR tax code
can any body please suggest me
Thanks in advance
Bhushan

Hi Sri Nath
My requirement is i want to split the posting of revenue account in two lines .like
gl code
30000     300   with A0 tax code
30000     700    with AR tax code
And taxes are posting correctly in their respective Gl accounts.
Regards
Bhushan Kolte

Enter a name and city for one-time account posting is the message i get

Enter a name and city for one-time account posting is the message i get ,when i am trying to post a onetime vendor .I have entered name ,country and language when the pop comes.But still throws me this message ,pls help.

Hi,
I didnt understand what u mean by "when i am trying to post a onetime vendor".
Pl. specify whether you are:
-Creating a OTV
-Creating a PO for a OTV
or
doing any other transaction
Regards,
Prithviraj

Error when creating Final Accounting Post to GL in AR

Hello,
I currently getting an error while creating Final Accounting Post to GL
I have changed the Profile Option SLA: Enable Trace to <null> as mentioned in the solution on metalink. But still I'm getting this error.
If anyone has encountered the error(LOG) below; please reply me as soon as possible
thanks
mevin
THE LOG
Subledger Accounting: Version : 12.0.0
Copyright (c) 1979, 1999, Oracle Corporation. All rights reserved.
XLAACCPB module: Create Accounting
Current system time is 14-AUG-2009 09:36:54
XDO Data Engine Version No: 5.6.3
Resp: 50832
Org ID : 102
Request ID: 499751
All Parameters: P_APPLICATION_ID=222:P_SOURCE_APPLICATION_ID=:P_DUMMY=:P_LEDGER_ID=2089:P_PROCESS_CATEGORY_CODE=:P_END_DATE=:P_CREATE_ACCOUNTING_FLAG=N:P_DUMMY_PARAM_1=:P_ACCOUNTING_MODE=:P_DUMMY_PARAM_2=:P_ERRORS_ONLY_FLAG=N:P_REPORT_STYLE=D:P_TRANSFER_TO_GL_FLAG=Y:P_DUMMY_PARAM_3=:P_POST_IN_GL_FLAG=Y:P_GL_BATCH_NAME=:P_MIN_PRECISION=2:P_INCLUDE_ZERO_AMOUNT_LINES=:P_REQUEST_ID=:P_ENTITY_ID=118514:P_SOURCE_APPLICATION_NAME=:P_APPLICATION_NAME=:P_LEDGER_NAME=:P_PROCESS_CATEGORY_NAME=:P_CREATE_ACCOUNTING=:P_ACCOUNTING_MODE_NAME=:P_ERRORS_ONLY=:P_ACCOUNTING_REPORT_LEVEL=:P_TRANSFER_TO_GL=:P_POST_IN_GL=:P_INCLUDE_ZERO_AMT_LINES=:P_VALUATION_METHOD_CODE=:P_SECURITY_INT_1=:P_SECURITY_INT_2=:P_SECURITY_INT_3=:P_SECURITY_CHAR_1=:P_SECURITY_CHAR_2=:P_SECURITY_CHAR_3=:P_CONC_REQUEST_ID=:P_INCLUDE_USER_TRX_ID_FLAG=:P_INCLUDE_USER_TRX_IDENTIFIERS=:P_USER_ID=:DebugFlag=
Data Template Code: XLAACCPB
Data Template Application Short Name: XLA
Debug Flag:
{P_ACCOUNTING_REPORT_LEVEL=, P_DUMMY=, P_ACCOUNTING_MODE_NAME=, P_ERRORS_ONLY_FLAG=N, P_REPORT_STYLE=D, P_GL_BATCH_NAME=, P_END_DATE=, P_SECURITY_INT_3=, P_SECURITY_INT_2=, P_SECURITY_INT_1=, P_VALUATION_METHOD_CODE=, P_POST_IN_GL=, P_TRANSFER_TO_GL=, P_TRANSFER_TO_GL_FLAG=Y, P_INCLUDE_USER_TRX_IDENTIFIERS=, P_USER_ID=, P_PROCESS_CATEGORY_NAME=, P_ERRORS_ONLY=, P_DUMMY_PARAM_3=, P_SECURITY_CHAR_3=, P_DUMMY_PARAM_2=, P_SECURITY_CHAR_2=, P_DUMMY_PARAM_1=, P_SECURITY_CHAR_1=, P_ENTITY_ID=118514, P_PROCESS_CATEGORY_CODE=, P_INCLUDE_ZERO_AMT_LINES=, P_LEDGER_ID=2089, P_POST_IN_GL_FLAG=Y, P_APPLICATION_ID=222, P_INCLUDE_USER_TRX_ID_FLAG=, P_APPLICATION_NAME=, P_REQUEST_ID=, P_CONC_REQUEST_ID=, P_LEDGER_NAME=, P_SOURCE_APPLICATION_ID=, P_CREATE_ACCOUNTING=, P_CREATE_ACCOUNTING_FLAG=N, P_MIN_PRECISION=2, P_SOURCE_APPLICATION_NAME=, P_INCLUDE_ZERO_AMOUNT_LINES=, P_ACCOUNTING_MODE=}
Calling XDO Data Engine...
[081409_093744202][][EXCEPTION] SQLException encounter while executing data trigger....
java.sql.SQLException: ORA-20001: -: XLA-95103: An internal error occurred. Please inform your system administrator or support representative that:
An internal error has occurred in the program xla_create_acct_rpt_pvt.BeforeReport . ORA-20001: -: XLA-95103: An internal error occurred. Please inform your system administrator or support representative that:
An internal error has occurred in the program xla_accounting_pkg.accounting_program_document. ORA-01086: savepoint 'SP_EVENTS' never established
ORA-20001: -: XLA-95103: An internal
ORA-06512: at "APPS.APP_EXCEPTION", line 72
ORA-06512: at "APPS.XLA_EXCEPTIONS_PKG", line 110
ORA-06512: at "APPS.XLA_EXCEPTIONS_PKG", line 289
ORA-06512: at "APPS.XLA_EXCEPTIONS_PKG", line 162
ORA-06512: at "APPS.XLA_CREATE_ACCT_RPT_PVT", line 262
ORA-06512: at line 4
     at java.lang.Throwable.<init>(Throwable.java:57)
     at java.lang.Throwable.<init>(Throwable.java:68)
     at java.sql.SQLException.<init>(SQLException.java:55)
     at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:112)
     at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:331)
     at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:288)
     at oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java:745)
     at oracle.jdbc.driver.T4CCallableStatement.doOall8(T4CCallableStatement.java:215)
     at oracle.jdbc.driver.T4CCallableStatement.executeForRows(T4CCallableStatement.java:965)
     at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1170)
     at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3339)
     at oracle.jdbc.driver.OraclePreparedStatement.execute(OraclePreparedStatement.java:3445)
     at oracle.jdbc.driver.OracleCallableStatement.execute(OracleCallableStatement.java:4394)
     at oracle.apps.xdo.dataengine.XMLPGEN.executeTriggers(XMLPGEN.java:699)
     at oracle.apps.xdo.dataengine.XMLPGEN.processData(XMLPGEN.java:255)
     at oracle.apps.xdo.dataengine.XMLPGEN.processXML(XMLPGEN.java:205)
     at oracle.apps.xdo.dataengine.XMLPGEN.writeXML(XMLPGEN.java:237)
     at oracle.apps.xdo.dataengine.DataProcessor.processData(DataProcessor.java:364)
     at oracle.apps.xdo.oa.util.DataTemplate.processData(DataTemplate.java:236)
     at oracle.apps.xdo.oa.cp.JCP4XDODataEngine.runProgram(JCP4XDODataEngine.java:293)
     at oracle.apps.fnd.cp.request.Run.main(Run.java:157)
Start of log messages from FND_FILE
14-AUG-2009 09:37:19 - Beginning of the Report
GL Inerface tablename = GL_INTERFACE
GL Inerface tablename = GL_INTERFACE
tablename = GL_INTERFACE
14-AUG-2009 09:37:19- Submitting the Journal Import
GL Inerface tablename = GL_INTERFACE
GL Inerface tablename = GL_INTERFACE
tablename = GL_INTERFACE
14-AUG-2009 09:37:19- Submitting the Journal Import
14-AUG-2009 09:37:44- Journal Import completed
ORA-20001: -: XLA-95103: An internal error occurred. Please inform your system administrator or support representative that:
An internal error has occurred in the program xla_create_acct_rpt_pvt.BeforeReport . ORA-20001: -: XLA-95103: An internal error occurred. Please inform your system administrator or support representative that:
An internal error has occurred in the program xla_accounting_pkg.accounting_program_document. ORA-01086: savepoint 'SP_EVENTS' never established
ORA-20001: -: XLA-95103: An internal
ORA-06512: at "APPS.APP_EXCEPTION", line 72
ORA-06512: at "APPS.XLA_EXCEPTIONS_PKG", line 110
ORA-06512: at "APPS.XLA_EXCEPTIONS_PKG", line 289
ORA-06512: at "APPS.XLA_EXCEPTIONS_PKG", line 162
ORA-06512: at "APPS.XLA_CREATE_ACCT_RPT_PVT", line 262
ORA-06512: at line 4
End of log messages from FND_FILE
Executing request completion options...
Finished executing request completion options.
Concurrent request completed
Current system time is 14-AUG-2009 09:37:45
---------------------------------------------------------------------------

select * from gl_je_sources_tl;
main columns to look at are:
IMPORT_USING_KEY_FLAG
je_source_name
je_source_key
user_je_source_name
select * from gl_je_categories;
main columns to look at are:
je_category_key
user_je_category_name
If import_using_key_flag is Y for your je_source (Receivables), for the application (222) you are running Create Accounting in Final Post Mode, then apply the patch 8568620
By
Vamsi

GL account Posting.

Hi gurus,
I am getting GL account file from third party.In that file I have to check the GL account and line Items and post to FB01 through Inbound IDOC.
In that file I have to check the GL account line items.
1. Suppose the account is not balanced that account post to the suspence account.
         ( They already given the suspense account no. )
             How we can post the account suspense account.?
2. Suppose The file contains cost center , but the GL account always suppressed the cost center, then also this goes to the suspence account.
           How we can check the Cost center in the above scenario.
3. checking Tax codes.
Hi gurus,
can any one guide me how to do these requirements.
               Thanks in Advance..
Thanks and Regards,
Abinavasiri

Hi abhinav,
The requirement is simple try to analyse the structure of the file with the IDOC structure that you are using while posting the data in R3.
1. Suppose the account is not balanced that account post to the suspence account.
( They already given the suspense account no. )
How we can post the account suspense account.?
Instead of normal GL Account you need to pass this suspense account no for the same glaccount field.
2. Suppose The file contains cost center , but the GL account always suppressed the cost center, then also this goes to the suspence account.
If you find cost center again map again use this suspense account.
3.There is field in the IDoc structure for Tax Code just pass the same.
Only here the logic you have to work around is the data that comes in files should be grouped according under a document and then map all the fields with the corresponding IDOC structure and post the data.
Let me know which IDOC you are using to post the GL document.
Thanks
Sudharshan

How to clear G/L account posting made through MM documents/movements

Hi Gurus,
How to clear G/L account posting made through MM documents/movements.
This is issue related to open item clearance .I want to clear all MM related postiongs happened through MM movements.( From PO,invoice etc)
Regards,
nitin

Hi,
Only GR/IR account is maintained as open item management. use t-code f.19 or f.13
Regards,
Sreekanth

Split Accounting Document on the basis of SD Billing Document

Dear All,
When we create an SD Invoice, system generates an Accounting Document too. Any idea as to which program / interface does this?
Also, is it possible that I can split the Customer line item in FI Document? Please see the example below:
As it happens in SAP
Billing Document:
Item 10 - Rs. 1000
Item 20 - Rs.   500
Accounting Document:
Customer A/c Debit      Rs. 1500
     Revenue 1 Credit     Rs. 1000
     Revenue 2 Credit     Rs.   500
What is required
Billing Document:
No Change
Accounting Document:
Customer A/c Debit      Rs. 1000
Customer A/c Debit     Rs.   500
     Revenue 1 Credit     Rs. 1000
     Revenue 2 Credit     Rs.   500
Thanks in advance,
Shalin Shah

Hi Shalin,
Did you find any solution to this ?
I have a similar requirement for one of the client as they dont want the delivery/invoice to get split from SD and we cant do FI summarization due to certain other limitations.
The only option that I see is to split accounting document when it is getting created from Billing. I did happen to find one of the user exit EXIT_SAPLV60B_008, but unsure if it can really help solve the purpose when document clearing, debit credit notes and cancellation happens.
Regards,
AS

Employee Vendor Account posting

hi all.
i have to configure the Vendor Accounts posting.
there are few wage types, that need to be posted to employee vendors in FI.
If the following wage types are to be posted, please explain me the following one.
wage type : 1122 personal expenses
wage type :1123 Business expenses
symbolic account :1122
symbolic account : 1123
i have used the same for both wage types and symbolic accounts.
employee vendor numbers : 50001, 50002, 50003, 50004.
please let me know whether, under the node of Posting in IMG, should i take all these vendors and link the symbolic account or any other porcedure.like shown below.
1122-50001
1122-50002
1122-50003
1122-50004
1123-50001
1123-50002
1123-50003
1123-50004
is this how i should link all the vendor to the concerned Symbolic accounts.
please give me a solution. .
waiting for your reply
prathap

hi all .
i am really thankful to all of you.
i have Basic, HRA, Transportation, Food allowance.
for the month April, i have made the test data and confirmed that the G/L accounts are readily available in FI.there is no problem in posting.
but when i tried to post the salary advance payment to vendor account, it is throwing error.
i have configured, as follows
created Symbolic account with the specification K
assigned the symbolic account to the wage type
assigned *0002 to the symbolic account.
when i tried to post to accounts, it is throwing the error. i am sure that the error is only because of this.
i have cross checked whether the vendor account is created in FI , which is available.
please tell me apart from this configuration, any thing is missing.
please help me.
prathap

Account posting for the GR of subcontract PO

Hi experts;
We have a special requirement about the account posting for the GR of subcontract PO, 3POP process is used here means we create the SO, PR is created automatically. then convert to PO (Account assignment 'E', subcontract PO) . Basically now when the account document is created upon GR of the PO (101 E for FGI, 543 O for Component), the posting is like below:
Itm PK CoCd Account Account short text     Amount in LC LCurr         Amount Crcy      LC2 amount Trs
    1 89 1000 792000   Finished goods inven        100.00 EUR          100.00 EUR                  BSX
    2 96 1000 191100   Goods Rcvd/Invoice R         90.00- EUR           90.00- EUR                  WRX
    3 91 1000 893010   Cost of goods sold          100.00- EUR          100.00- EUR                  BSV
    4 86 1000 417001   Purchased services           90.00 EUR           90.00 EUR                  FRL
    5 99 1000 300000   Inventory - Raw Mate         20.00- EUR           20.00- EUR                  BSX
    6 81 1000 400020   Raw materials consum         20.00 EUR           20.00 EUR                  GBB
Then the requirement is that the line item 3,4 should be combined together and 10.00- value posted. (Maybe then the transaction is BSV or PRD?)
Anybody know how to fit this gap? kindly telll me. Appreciate!
Hoping for a positive & prompt response

Hi Gaito,
Thanks! but this configuration is not the right one. This is for the different posting like below. But can't conbine BSV and FRL into together.
Posting schema without price differences:
Stock account FERT : 400 +
Stock change : 400 -
GR/IR clearing acct : 250 -
External service acct : 250 +
Compon. stock account : 100 -
Consumption account : 100 +
Posting schema with price differences:
Stock account FERT : 400 +
Stock change : 350 -
Price difference : 50 -
GR/IR clearing acct : 250 -
External service acct : 250 +
Compon. stock account : 100 -
Consumption account : 100 +
Regards
Jimmy

Account Posting in Case of Subcontracting

Hi Experts,
How do we map Account posting in case of Subcontracting..
Do we post something to Customer Account?? Or posting is only in G/L Accounts..??
Thanks in Advance..
Regards,
HP

Closing the thread because of no response..

Dont want account posting while return

Dear All
I am facing one problem in one scenario.
In return case i dont want one condition type to post. i dont want post one condition in that particular account. i am using the same pricing procedure for sales cycle and return sales. and that condition should be post in sales ( now it is posting correctly ) but i dont want want to post in when i create return billing document. can u please tell me how should i handle it in pricing procedure,i cant find anything in condition type about account posting. but i think i can handle in pricing procedure by using new requirement . and the logic should be while creating return order the value of that condition should pickup zero. am i right ? please give me ur guidance
Thanks and Regards
Bhushan Kolte

Hi,
Based on your requirement, two options are available.
1. Write a new requirement ( transaction VOFM) and assign tit to condition type with a ABAP code if doc type is return the condition gets disqualified.
2. Alternatively you can write new condition base value and make it to zero when dco type is return ( transaction VOFM) and assign it to the condition in pricing procedure

Report for list of invoce for that accounting posting is due

Hi,
Is there is any report to see the list of invoice for that accounting posting has not done.Please reply ASAP.
Regards
Prabudh

Hi
Go to T code VF05n and check open Billing documents and execute. System gives you the list which are pending for posting to FI.
Regards

BAPI for transaction FB01 with account posting key

Hi,
I have to use a BAPI for registering Invoices into the FI module through the FB01 transaction.
I am trying to use the standard BAPI: BAPI_ACC_DOCUMENT_POST
The problem is that this BAPI does not manage the account posting key (field BSCHL).
Could anyone provide help?
Thank you very much in advance.

It is happening here in the BAPI
CALL FUNCTION 'FI_GET_POSTING_KEY'
         EXPORTING
              i_ktosl       = gs_accit-ktosl
         IMPORTING
              e_bschs       = ld_bschs
              e_bschh       = ld_bschh
              e_umskz       = ld_umskz
         EXCEPTIONS
              error_message = 1.
As max pointed out, it is dependent on the transaction key(KTOSL).
Srinivas

Split Account posting

Similar Messages

Maybe you are looking for