Date in GL Account Posting ?

I am posting the GL a/c line items using BAPI_ACC_GL_Doc_post ...!!
In the flat file , i get the dates as '01/01/2006' and i convert it to 8 format by using :
split and concatenate .
The internal table (line_t) for line items has posting date as '01012006' , when i debug ...but then I keep on getting this error message : ' 20/06/0101 is incorrect in item 001...!! Though the line table has date has '01012006' , the BAPI returns this message ?
Can anyone tell what can be the issue ?

Hi
You have to insert the date in the format YYYYMMDD:
If DATE_IN = 01/01/2006 =>
DATE_OUT(4) = DATE_IN+6(4).
DATE_OUT4(2) = DATE_IN3(2).
DATE_OUT+6(2) = DATE_IN(2).
Max

Similar Messages

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

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

Require standard BAPI for GL Account Posting

We are creating a GL Account Posting in Transaction F-02.
We are giving Document date Document type Posting Date, Currency type , Company code, Posting Key AccountNo, Amount.
Click on Save Button . A screen appears. Then the Document is Parked. A document No is generated.
i want a standard BAPI which does this Process

Hi,
Check the BAPI's
<b>BAPI_ACC_DOCUMENT_POST
BAPI_INCOMINGINVOICE_PARK</b>
regards
vijay

Account posting keys involves for process of third party order

hi
pls tell me the process of third party order and whos account stock will be debited and tell me the account posting keys involves in this process and how it operates
regards
Ram
Edited by: Ian Wong on Aug 13, 2008 7:06 PM

THIRD PARTY SCENARIO
In third-party order processing, your company does not deliver the items requested by a customer. Instead, you pass the order along to a third-party vendor who then ships the goods directly to the customer and bills you. A sales order may consist partly or wholly of third-party items. Occasionally, you may need to let a vendor deliver items you would normally deliver yourself.
Process Flow
The processing of third-party orders is controlled via material types. Material types define whether a material is produced only internally, can be ordered only from third-party vendors, or whether both are possible. For example, a material that is defined as a trading good can only be ordered from a third-party vendor. However, if you manufacture your own finished products, you may also want, from time to time, to be able to order the same type of product from other vendors.
Processing Third-Party Orders in Sales
Third-party items can be created automatically by the system, depending on how your system is set. However, you can also change a standard item to a third-party item during sales processing manually.
Automatic third-party order processing
If a material is always delivered from one or more third-party vendors, you can specify in the material master that the material is a third-party item. During subsequent sales order processing, the system automatically determines the appropriate item category for a third-party item: TAS. To specify a material as a third-party item, enter BANS in the Item category group field in the Sales 2 screen of the material master record.
Manual third-party order processing
In the case of a material that you normally deliver yourself but occasionally need to order from a third-party vendor, you can overwrite the item category during sales order processing. For a material that you normally deliver yourself, you specify the item category group NORM in the material master.
If, as an exception, you use a third-party material, change the entry TAN to TAS in the ItCa field when processing the sales document. The item is then processed as third-party item.
If address data for the ship-to party is changed in the sales order in third-party business transactions, the changed data will automatically be passed on to purchase requisition and also to the purchase order ,if one already exists. In the purchase order, you can display the address data for the ship-to party in the attributes for the item.
You can only change the address data for the ship-to party in the sales order for third-party business transactions, and not in the purchase order.
Processing Third-Party Orders in Purchasing
When you save a sales order that contains one or more third-party items, the system automatically creates a purchase requisition in Purchasing. Each third-party item in a sales order automatically generates a corresponding purchase requisition item. During creation of the requisition, the system automatically determines a vendor for each requisition item. If a sales order item has more than one schedule line, the system creates a purchase requisition item for each schedule line.
Purchase orders are created from purchase requisitions in the usual way. For more information about creating purchase orders, see the Purchasing documentation. During creation of the purchase order, the system automatically copies the delivery address of your customer from the corresponding sales order. In a sales order, you can enter purchase order texts for each third-party item. When you create the corresponding purchase order, the texts are automatically copied into the purchase order. The number of the purchase order appears in the document flow information of the sales order.
All changes made in the purchase order are automatically made in the sales order as well. For example, if the vendor confirms quantities and delivery dates different from those you request and enters them in the purchase order, the revised data is automatically copied into the sales order
You process third-party items by creating a normal sales order. In overview for the order, you can then overwrite the default item category (TAN in the standard system) with the special item category for third-party items: TAS
Billing Third-Party Orders
If relevance for billing indicator for the item category has been set to B (relevant for order-related billing on the basis of the order quantity) in Customizing, the system includes the order in the billing due list immediately. If, however, the indicator has been set to F (relevant to order-related billing on the basis of the invoice quantity), the system does not include the order in the billing due list until an invoice from the vendor has been received and processed by the purchasing department. In the standard system, item category TAS (third-party order processing) has been given billing-relevance indicator F.
In the first case, the third-party order is considered to be completely billed only when the invoiced quantity equals the order quantity of the sales order item. In the second case, each time a vendor invoice is received, a customer invoice is created for the quantity in the vendor invoice and the order is considered to be fully invoiced until the next vendor invoice is received.
If you have activated billing-relevance indicator F for item categories in Customizing, billing can refer to the goods receipt quantity instead of the incoming invoice quantity.
You can control whether the invoice receipt quantity or the quantity of goods received is relevant for billing in Customizing for copying control for billing at item level.
FOR YOUR PROCESS Individual Purchase Orders WELL GIVE THE RIGHT SOLUTION
Individual purchase orders are used when your customer orders goods from you that are not in stock and must be ordered from one or more external vendors.
Process Flow
During sales order entry, the system automatically creates a purchase requisition item. The purchasing department creates a purchase order based on the requisition and the vendor ships the goods directly to you (unlike third party order processing, where the vendor ships directly to your customer). You then ship the goods to your customer. While the goods are part of your inventory, you manage them as part of the sales order stock. Sales order stock consists of stock that is assigned to specific sales orders and cannot be used for other purposes.
Goods receipt will be posted when ever the vendor ships the goods to our customer.
We will do this transaction in SAP using MIGO.
Invoice receipt is done when the Vendor sends us the invoice.. ( I.e Billing ).
It can be done using MIRO.
THe above two steps are standard and manual. There are many other ways that the actual process can happen. If the client follows EDI standards then the Goods receipt and Invoice receipt can be done through IDOCs automatically.
Process Flow for 3rd Party Sales
Customize the third party sales in summary:
Prerequisites for 3rd party sales,
Purchasing org,
purchasing group,
assign the Purchase org to company code
assign Purchase org to plant,
should not maintain the stock in material, it should be trading goods,
1. Create Vendor XK01
2. Create Material Material Type as "Trading Goods". Item category group as "BANS".
3. Assign Item Category TAS to Order type that you are going to use.
4. A sale order is created and when saved a PR is generated at the background
5. With reference to SO a PO is created (ME21N). The company raises PO to the vendor.
6. Vendor delivers the goods and raises bill to company. MM receives the invoice MIRO
7. Goods receipt MIGO
8. Goods issue
9. The item cat TAS or Schedule line cat CS is not relevant for delivery which is evident from the config and, therefore, there is no delivery process attached in the whole process of Third party sales.
10. Billing *--
SD - 3rd party sales order Create Sales Order
VA01
Order Type
Sales org, distr chnl, div
Enter
Sold to
PO #
Material
Quantity
Enter
Save
SD - 3rd party sales order View the PR that is created with a third party sales order
VA01
Order Number
Goto Item Overview
Item ->Schedule Item
SD - 3rd party sales order View the PR that is created
ME52N
Key in the PR number
Save
SD - 3rd party sales order Assign the PR to the vendor and create PO
ME57
Key in the PR number
Toggle the "Assigned Purchase Requisition"
Execute
Check the box next to the material
Assign Automatically button
Click on "Assignments" button
Click on "Process assignment"
The "Process Assignment Create PO" box , enter
Drag the PR and drop in the shopping basket
Save
SD - 3rd party sales order Receive Goods
MIGO_GR
PO Number
DN Number
Batch tab , click on classification
Serial Numbers tab
Date of Production
Flag Item OK
Check, just in case
Post
Save
SD - 3rd party sales order Create Invoice
MIRO
Invoice Date
Look for the PO , state the vendor and the Material
Check the box
Click on "Copy"
Purchase Order Number (bottom half of the screen)
Amount
State the baseline date
Simulate & Post
Invoice Number
*Invoice blocked due to date variance
SD - 3rd party sales order Create a delivery order
VL01N
In the order screen , go to the menu Sales Document , select "Deliver"
Go to "picking" tab
State the qty and save
SD - 3rd party sales order Create a billing document
VF01
Ensure that the delivery document is correct in the
Enter
Go to edit -> Log
Save
Third party order processing is as follows:
Assume three companies X, Y and Z
X - The company,
y - The customer
Z - Vendor
When ever X gets a PO from Y to supply some goods, X has an option of either manufacturing those goods or procuring those goods.
If he is procuring the goods, there are two methods that are generally followed:
Method 1) After receiving the PO from Y, X creates a sales order against Y.
Now at the same time he also creates a PO to a vendor Z to produce the goods
Z produces the goods and supplies to X
X receives the goods from Z
Then X delivers the same goods to Y.
After that X invoices Y and Z invoices X.
Note : Here there is no direct/ Indirect relation between Z and Y.
This process is known as Trading Process. and the Material here is created with Material type HAWA.
The other method is a Third party order processing method:
Here the glaring difference is that instead of Z supplying the material to X and X in turn supplying the same material to Y.
X authorizes Z to supply the material to Y on his behalf and notify him once the delivery is complete.
Now Z supplies the material to Y and acknowledges the same to X.
Z will send a copy of delivery acknowledgement and invoice to X.
After receiving the delivery confirmation and invoice from Z, X has to verify the invoice and this process is known as invoice verification and is done in SAP through Tcode MIRO.
The next step for X is to create an invoice and submit to Y
Only after the invoice verification document is posted then only X can create an invoice for Y.
This is the business flow that is followed for third party order configuration.
There are few steps that have to be configured to enable the system to function as mentioned above.
Step1)
If you are always following a third party process for a material then you have to create the material using item category group BANS.
The procurement type should be marked as External procurement (F) in MRP 2 view of the material master record.
if you are not always allowing third party order processing then u can create a material master record with item category group as NORM and the procurement type should be marked as ( X) meaning both types of procurement ( in house manufacturing and external procurement).
Step 2)
the item category in the order should be manually changed as TAS.
For that you need to configure the item category determination
Order type + item cat Group + Usage + High level = Item cat + Manual item cat
OR + NORM + + = TAN + TAS
OR + BANS + + = TAS
Step 3)
make sure that during the item category configuration for TAS you need to mark relevant for billing indicator as F
step 4)
The schedule line category for this type should be CS.
make sure that you mark subsequent type as NB - purchase requisition in this schedule line category as this will trigger the purchase requisition order immediately after the creation of the sales order and the PO to vendor is created against this purchase requisition.
Award if Helpful,
Regards
Priyanka.P

Copy Data for Multiple Accounts from LegalApp to FinanceApp

Hi Experts,
I have two application, LegalApp and FinanceApp, wherein both have P&L Accounts but with different set of accounts. I have to copy the data of LegalApp P&L Accounts to my FinanceApp P&L Accounts. Some accounts in the FinanceApp have the same ID to that of the LegalApp so I don't have difficulty copying the data. I've used the Script Logic below:
*DESTINATION_APP = FINANCE
*ADD_DIM COSTCENTER=NO_COSTCNTR
*ADD_DIM MARKET=NO_MARKET
*ADD_DIM PRODUCT=NO_PRODUCT
*ADD_DIM CUSTOMER=NO_CUSTOMER
*RENAME_DIM ACCOUNT=COPAACCOUNT
*SELECT(%LegalAcc%,"ID","ACCOUNT","IS_COPY='Y'")
*XDIM_MEMBERSET ACCOUNT=%LegalAcc%
*XDIM_MEMBERSET ENTITY=DMPI
*XDIM_MEMBERSET DATASRC=<ALL>
*WHEN *
*IS *
*REC(FACTOR=1)
*ENDWHEN
*COMMIT
What I'm having trouble is copying data from LegalApp Accounts to FinanceApp Accounts whos ID's are not the same.
Example: from PN0000000000 to COPA00000000. I've tried inserting the following logic but still nothing happened.
*WHEN ACCOUNT.ID
*IS "PN0000000000"
*REC(ACCOUNT="COPA00000000")
*ENDWHEN
Hope you could help me.
Thanks,
Marvin

Hi nilanjan,
I've already tried that(see post above) and that doesn't seem to work.
*DESTINATION_APP = FINANCE
*ADD_DIM COSTCENTER=NO_COSTCNTR
*ADD_DIM MARKET=NO_MARKET
*ADD_DIM PRODUCT=NO_PRODUCT
*ADD_DIM CUSTOMER=NO_CUSTOMER
*RENAME_DIM ACCOUNT=COPAACCOUNT
*SELECT(%LegalAcc%,"ID","ACCOUNT","IS_COPY='Y'")
*XDIM_MEMBERSET ACCOUNT=%LegalAcc%
*XDIM_MEMBERSET ENTITY=DMPI
*XDIM_MEMBERSET DATASRC=<ALL>
*WHEN ACCOUNT.ID
*IS "PN0000000000"
*REC(ACCOUNT="COPA00000000")
*ENDWHEN
*COMMIT
I was wondering if I'm missing something in my statement.
Thanks,
Marvin

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.

Error Message at F-02 "Enter Name & city for One-time account posting"

While create JV in one time customer ledger through F-02, following error message appeared & system not allow to crate JV.
"Enter Name & city for One-time account posting", Please help
Regards
BK GAIKWAD

Hi
Are you having separate account group for this One time vendor?
Via this account group, the vendor-specific fields, such as name, address, and bank address data should be changed from suppressed to display when you enter the vendor master record. You need to enter this data when you enter the document.
Check the fields status of Name, city etc in the below path
SPRO - Financial Accounting - Accounts receivable and accounts payable - Vendor accounts - MAster data - Preparations for creation of master data - Define account group with screen layout
Regards
Malathi

What is the Account posting for Commissions

Hi All,
If there is any account posting done for commissions during the transactions like A/R Invoice?
If yes, then please tell me about the journal in detail and accounts in which it is posted.
Thanx & Regards
Sibasish

Commissions can be defined for a sales employee, an item, or a customer. The commission is determined when a sales document is entered and saved for all the rows in the document. The Commission Groups define the commissions that are given internally to the sales employees. The commissions are calculated in a report, (Tools -> Queries ->System Queries -> SP Commission by Invoices in Posting Date Cross-Section) and are not posted to any accounts.

Delete master data of GL account

sir
please give me detail
we want to delete the master data of GL account
ritu

Hi,
have look at
https://www.sdn.sap.com/irj/sdn/forums
sorry made a mistake...
If no posting has been done, the try OBR2...
If the hint is useful Say thanks by reward.
Regards,
Prabhu Rajesh
Message was edited by:
PrabhuRajesh Janardanan

Accounts posting while creating the debitmemo.

Hello SDNs,
I will have to configure debitmemo process to my client.. So i will define the new document types..and i will maintain the copy controls.. After completing the configuration. How i will maintain the account determination settings..Please explain the account determination process after creating the debitmemo.. My client is asking specially on account determination after creating the debitmemo..
Please explain the accounts (GL accounts)settings and process after creating the debitmemo..
Thanks,
KV

Hi
For debit memo also you need to fallow account determination procedure.
Process:
1.check master data relevent for account assignment,here you define the account groups relevent for customer/material.
2.define dependencies of revenue account determination,here create table with required fields.
3.define access sequences and account determination types,here assin access sequence to condition type.
4.Define and assign account determination procedure,here assign account determination procedure to billing type ex:assign it to debit memo,based on this link accounts will be posted to right account.
5.Define & assign Account Key,here assign account keys to pricing procedure,this is the intigration point betn pricing & account determination.
6.assign G/L accounts,here based on table fields & conditon type,chart of accouts etc g/l account will be mapped.
If you want based on billing doc values needs to be posted to different g/l accounts you can take billing type as one field in defined table so that different billing doc will be posted to different g/l accounts.
Regards,
RAM

Data is not getting posted in ABAP Proxy.

Hi,
I am working on File to ABAPProxy scenario. The data is not going to proxy.
In PI sxmb_moni is status is successfull and in the R3 sxmb_moni the status is successfull. But the data is not getting posted in the tables(ABAPProxy). I had checked the inbound and oubound queues. And with the same input data, abapers cheked their code in Abapproxy, then the table is getting updated. When we trigger from PI, the tables are not getting updated.Please help me.
Thanks,
Pragathi.

Hi,
The problem may be
Case 1: Cache is not getting refreshed(Check SXI_CACHE)
Case 2: The Queue Is blocked (Check SMQ1 & SMQ2)
Regards,
Sainath

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

How do I delete one of the user accounts on my computer and not lose the data in that account?

How do I delete one of the user accounts on my computer and not lose the data in that account?

I actually have the opposite of this problem. haha.
https://discussions.apple.com/thread/4484354

Date in GL Account Posting ?

Similar Messages

Maybe you are looking for