BAPI_ACC_DOCUMENT_POST

Former Member — Fri, 18 Jul 2008 16:33:53 GMT

I am not sure in filling up the import parameters for BAPI_ACC_DOCUMENT_POST.

Am changing the reason code for the FI document. What will be the value for the below parameters.

DOCUMENTHEADER-OBJ_TYPE

DOCUMENTHEADER-OBJ_KEY

DOCUMENTHEADER-BUS_ACT

Regards

Anand

Re: BAPI_ACC_DOCUMENT_POST

naimesh_patel — Fri, 18 Jul 2008 16:43:26 GMT

You will find good documentation in the BAPI transaction.

Go to BAPI

Select the tab Alpabetical

Select the AcctngDocument

Select the method post

select the parameter .. DocumentHeader

Select tab Documentation.

Regards,

Naimesh Patel

Re: BAPI_ACC_DOCUMENT_POST

Former Member — Fri, 18 Jul 2008 17:21:35 GMT

Hello Anandan,

Check the BAPI documentation :

Header

Description

Parameters for the transfer of document header data.

The following fields must be filled:

OBJ_TYPE Sender identification

OBJ_KEY Reference number of source document

OBJ_SYS Logical system of source document

COMP_CODE Company code

PSTNG_DATE Posting date

BUS_ACT Business transaction

USERNAME Document creator

Default

The field COMPO_ACC must remain empty for a general posting. If an SAP component is transferred in this field, a posting will only be made in this component. This function is only used for posting subsequently.

Source document

Description

When a business transaction is updated in Accounting, it may be that several documents are updated at the same time (FI document, CO document, etc). If the business transaction is not initiated in Accounting, a source document must exist outside Accounting. The information from this document must be transferred when the FI/CO interface is called up. The source information is updated in all accounting documents, and is made up of the following fields:

AWTYP (OBJ_TYPE) Reference transaction

Sender ID

AWKEY (OBJ_KEY) Reference key

Source document number

The reference key is made up of:

AWREF Reference document number (10 digits)

Source document number

AWORG Reference organizational unit (10 digits)

Number range ID (if required)

AWSYS (OBJ_SYS) Logical system

Logical system of source document

When the document is being processed, the system checks whether a reference document number (first part of the reference key) has been transferred.

Notes

Use a separate value in the OBJ_TYPE field (reference transaction). You must maintain an entry for this value in table TTYP, which could be a function module that is called when the user wants to branch back to the source/sender document from an accounting document. This makes it possible for documents updated using BAPIs to be included in the document navigation (revision). If you use SAP defined characters in the field OBJ_TYPE, errors can occur in the navigation.

The FI and CO line item suppression is defined separately for each reference transaction.

It is not necessary to separate the reference key into reference document number and reference organizational unit. This means that reference document numbers that are longer than 10 digits can be transferred into the reference key.

Check with the BKPF table with the BAPI input parameters data elements and field name descriptions.

Thanks,

Greetson

topic Re: BAPI_ACC_DOCUMENT_POST in Application Development and Automation Discussions

BAPI_ACC_DOCUMENT_POST

Re: BAPI_ACC_DOCUMENT_POST

Re: BAPI_ACC_DOCUMENT_POST