topic Re: BAPI_COPAACTUALS_POSTCOSTDATA Doc. Number in Application Development and Automation Discussions

BAPI_COPAACTUALS_POSTCOSTDATA Doc. Number

Former Member — Fri, 01 Jul 2005 10:31:57 GMT

Hello everyone!

I'm using BAPI_COPAACTUALS_POSTCOSTDATA to Post Costing-Based Actual Data.

The BAPI is working great, but it does not return the number of the generated document in the RETURN TABLE neiher in the sy-msg* fields.

I want this to display the generated document in the report.

Anyone has any tips on the subject?

Many thanks,

Ivo Martins

Re: BAPI_COPAACTUALS_POSTCOSTDATA Doc. Number

Former Member — Thu, 27 Oct 2005 14:18:26 GMT

I am experiencing the same problem as Ivo Martins; this BAPI appears to be posting correctly, but there is no confirmation in the RETURN table of the BAPI. Does any one have a suggestion ? I have checked OSS, but there does not seem to be any Notes to address this. Seems like all the BAPI's I have used previously provide some confirmation of the posting ( or an error message ) in the RETURN table

Thanks

Larry Parsons

Re: BAPI_COPAACTUALS_POSTCOSTDATA Doc. Number

Former Member — Fri, 28 Oct 2005 09:13:23 GMT

Hello Larry,

I can tell you in advance that there is no workaround for this situation.

The reason for this is not the BAPI itself, but another function that is at a more deep level that does the actual posting.

If you really need the Doc Numbers forget this BAPI.

Use KE21 or something like that.

Re: BAPI_COPAACTUALS_POSTCOSTDATA Doc. Number

ray_mannion — Sat, 01 Oct 2011 20:43:22 GMT

There is in fact a workaround to this issue. I see this question asked in lots of places so I figured I would post here:

4) Although the BAPI does not return the resulting document number and the forums say you cannot do it, this is a workaround that is somewhat hardcoding and requires familiarity with the data. In this example, we expect that the ww106 field is a unique value. Indeed, we went so far as to index the CE table. By specifying the ORDER BY clause, we can make sure we grab the most recent entry first. This is captured immediately after calling the BAPI and doing the BAPI_TRANSACTION_COMMIT and WAIT.

CALL FUNCTION 'BAPI...

CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'

EXPORTING

WAIT = 'X'

SELECT paobjnr pasubnr FROM ce41010 UP TO 1 ROWS

BYPASSING BUFFER

INTO (wa-paobjnr, wa-pasubnr)

WHERE ww100 = itab-key1

AND ww109 = itab-key2

AND ww106 = itab-key3

ORDER BY PAOBJNR DESCENDING PASUBNR DESCENDING

ENDSELECT.

There are a few tips and tricks for working with this BAPI posted here:

[http://raymannion.com/2011/bapi_copaactuals_postcostdata/|http://raymannion.com/2011/bapi_copaactuals_postcostdata/]

Re: BAPI_COPAACTUALS_POSTCOSTDATA Doc. Number

Former Member — Tue, 17 Apr 2012 11:30:35 GMT

Hi Ray,

Thanks alot for the solution, I was facing the same issue, and this comes as a life saver!

Currently my problem is that this select that you have suggested takes alot of time to run. In fact, it takes aroung 99% of the total conversion program runtime. Can you please suggest something to fix this?

Thanks in advance!

Neetha

Re: BAPI_COPAACTUALS_POSTCOSTDATA Doc. Number

Former Member — Fri, 18 Jan 2013 14:20:51 GMT

If you ad an additional characteristic to the where clause for TIMESTMP, and calculate it to be a minute or two prior to your posting, you will significantly speed up the performance....

Re: BAPI_COPAACTUALS_POSTCOSTDATA Doc. Number

VJ22 — Fri, 22 Nov 2013 10:46:10 GMT

Hi ,

I found another way to get generated copa document number .

so just sharing here .

kindly check

http://scn.sap.com/docs/DOC-49228