2013 May 15 12:56 PM
Hello Experts,
I am trying to use the BAPI BAPI_ACC_GL_POSTING_POST with Extension 1 for FBS1 Posting. I also need to update the Planned Reversal Date.
At the moment the BAPI Structure does not have STODT i.e. planned reversal date field.
Does this work for FBS1 Accural/Deferral Posting wherein we have to specify the planned reversal date?
Regards,
Manu
2013 May 15 1:53 PM
Hello Experts,
I am trying to use the BAPI BAPI_ACC_GL_POSTING_POST with Extension 1 for FBS1 Posting. I also need to update the Planned Reversal Date.
At the moment the BAPI Structure does not have STODT i.e. planned reversal date field.
Does this work for FBS1 Accural/Deferral Posting wherein we have to specify the planned reversal date?
Regards,
Manu
2013 May 15 1:07 PM
Hi,
Instead of BAPI why don't you write the BDC for the same.
If you want to use BAPI you need to add that required field in structure "BAPIACHE08" which is used in BAPI.
Regards,
R.S.K
2013 May 15 1:41 PM
BAPI are always better and robust than the sequence of screens. There is an extension provided in the BAPI. See note 487722.
Just wanted to know if you anyone has used it to update Planned Reversal Date as I couldn't find anyone using it successfully.
Regards,
Manu
2013 May 15 1:53 PM
2013 May 15 2:17 PM
Thanks Raymond,
I just checked the BADI. It seems that it is not called with my current BAPI i.e. BAPI_ACC_GL_POSTING_POST
Also checked the Documentation for this BADI.
This BAdI is called up within the BAPIs AcctngDocument.CHECK and AcctngDocument.POST ( BAPI_ACC_DOCUMENT_CHECK and BAPI_ACC_DOCUMENT_POST).
Seems I have to change the BAPI to use it.
Does it work that ways? I don't have an issue using another BAPI as long as my documents get posted with the planned reversal date.
Regards,
Manu
2013 May 15 4:47 PM
Hi Raymond,
Have you tried updating the planned reversal date using the BAPI BAPI_ACC_DOCUMENT_POST with the BADI BAdI ACC_DOCUMENT?
Does it work?
Regards,
Manu
2013 May 15 6:17 PM
Usually I use the generic BAPI_ACC_DOCUMENT_POST, and yes it worked fine for some standard (but never had to change this one) as well as every specific customer fields added to coding block. Maybe the older BAPI you used don't call the BAdI and only the old customer-exits of ACBAPI01, look before changing BAPI ?
The other solution I'm used to is use of FI/CO substitutions, you could also search this area. (Like export data to memory, and import it in substitution exit)
Regards,
Raymond
2013 May 20 11:52 AM
I explored the options with the USER EXIT and it worked with it.
Thanks for your help.
Regards,
Manu
| User | Count |
|---|---|
| 3 | |
| 2 | |
| 2 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |