topic Re: Parking Document Problem in Application Development and Automation Discussions

Parking Document Problem

Former Member — Thu, 23 Aug 2012 03:01:57 GMT

Hi all,

We are facing an issue in FI documents Parking to SAP,

At present we are using Function Module 'PRELIMINARY_POSTING_FB01' for FI document parking, by using this function module we could not capture any FI standard errors.

Findings:

We searched in net and came to know that, FI parking validations cannot be captured (FI validations can only be captured when posting is done - OSS notes 158739)

Also, we got to know that by using BAPI_ACC_GL_POSTING_POST and Customer Exit (CMOD) ACBAPI01 we can capture FI standard errors.

Doubts:

Can we look for any stimulation BAPI's before using PRELIMINARY_POSTING_FB01 function module to capture any FI errors?

Is there any stimulation BAPI's if available for FI parking?

Is there a way to capture FI standard errors during FI Parking other than usingBAPI_ACC_GL_POSTING_POST and Customer Exit (CMOD) ACBAPI01?

Waiting for your replies.....

Re: Parking Document Problem

Former Member — Thu, 23 Aug 2012 07:19:15 GMT

Hi,

As i suggest you use first try to check with Custom exit, if it doesnt work u can use bapi as second option. I could not find any other options other then this.

Re: Parking Document Problem

Former Member — Tue, 28 Aug 2012 04:12:00 GMT

Hi,

Thanks for your reply goutam...We have implemented BAPI + Customer exit + BTE events(Using for passing posting key)....

Again just for a clarification...In our case FB01 posting customization is such that for 40 and 50 only GL code is allowed,other than 40 and 50 posting keys (say 31, 29, etc...) vendor number is passed as Gl Number..But when i try to pass vendor number as GL number in BAPI, Customer Exit, BTE events,i am getting the errors as Vendor number(Say1234) cannot be passed in GL field...

Here i tried manually posting in FB01...everything is going well...

Waiting for your replies...

Re: Parking Document Problem

former_member209818 — Tue, 28 Aug 2012 04:43:32 GMT

If I am not wrong, BAPI_ACC_GL_POSTING_POST need a Explicit BAPI_COMMIT. So you can call BAPI and after execution, if you Use BAPI ROLLBACK, then probably you may be able to capture the errors. But if BAPI is successful, you may need to do the through testing, whether BAPI is consuming the Number range or not..

Harshad

Re: Parking Document Problem

Former Member — Tue, 28 Aug 2012 05:35:46 GMT

Hi,

Thanks for your reply..We are posting the FI documents via BAPI_ACC_GL_POSTING_POST BAPI.

But In our case FB01 posting customization is such that for 40 and 50 only GL code is allowed,other than 40 and 50 posting keys (say 31, 29, etc...) vendor number is passed as Gl Number..But when i try to pass vendor number as GL number in BAPI, Customer Exit, BTE events,i am getting the errors as Vendor number(Say1234) cannot be passed in GL field...

Here We tried manually posting in FB01...everything is going well...

Jagan

Re: Parking Document Problem

RaymondGiuseppi — Tue, 28 Aug 2012 06:40:52 GMT

BAPI_ACC_GL_POSTING_POST is for GL Account only, if you want to post to vendor account use an ACC BAPI which allows this like BAPI_ACC_INVOICE_RECEIPT_POST (vendor invoice) or the generic BAPI_ACC_DOCUMENT_POST.

Also most BAPI_ACC_XXXXX_POST are associated with a BAPI_ACC_XXXXX_CHECK to perform controls before actually posting.

Regards,

Raymond

Re: Parking Document Problem

Former Member — Tue, 28 Aug 2012 11:06:33 GMT

Hi all,

Thanks a lot for all of your sincere efforts in helping me out...

have used BAPI_ACC_DOCUMENT_POST + FIBF (BTE) to resolve my problem.

passed my GL code info to ACCOUNTGL and Vendor Related info to ACCOUNTPAYABLE and customer related info to ACCOUNTPAYABLE.Also Posting Key to EXTENSION1,Have passed BUS_ACT field in DOCUMENTHEADER in above BAPI....

Thanks a million to all....