Any Experience with CO-PA Planning BAPI BAPI_COPAPLANNING_POSTDATA?

[Former Member]

Hi All,

Does anyone have experience with the CO-PA planning BAPIs BAPI_COPAPLANNING_GETDATA and BAPI_COPAPLANNING_POSTDATA?

From reading the BAPI documentation, it looks like BAPI_COPAPLANNING_POSTDATA will post multiple records (depending on what was selected via the import parameters) all at once? Does this BAPI need a “comment work”? I assume so.

Is there a record limit to the amount of planning records that can be updated all at once?

Has anyone experienced any issues with BAPI BAPI_COPAPLANNING_POSTDATA posting a large amount of records (12,000)?

The BAPI looks like it handles the delta processing.

We are in the process of thinking of interface planning data into CO-PA planning and would like to know if it is feasible to load about 12,000 in a fairly quick amount of time.

Currently, we do not have the CO-PA Planning Framework (KEPM) configured, but might in the future.

Thanks,

Mike Vondran

eBay Inc.

[Former Member]

Hi All,

Does anyone have experience with the CO-PA planning BAPIs BAPI_COPAPLANNING_GETDATA and BAPI_COPAPLANNING_POSTDATA?

From reading the BAPI documentation, it looks like BAPI_COPAPLANNING_POSTDATA will post multiple records (depending on what was selected via the import parameters) all at once? Does this BAPI need a “comment work”? I assume so.

Is there a record limit to the amount of planning records that can be updated all at once?

Has anyone experienced any issues with BAPI BAPI_COPAPLANNING_POSTDATA posting a large amount of records (12,000)?

The BAPI looks like it handles the delta processing.

We are in the process of thinking of interface planning data into CO-PA planning and would like to know if it is feasible to load about 12,000 in a fairly quick amount of time.

Currently, we do not have the CO-PA Planning Framework (KEPM) configured, but might in the future.

Thanks,

Mike Vondran

eBay Inc.

[Former Member]

Hi Mike,

Rather than using the bapi's, for mass data transfer use tx KEFC. You can configure it in customizing (CO->PA->Tools->Data Transfers between CO-PA...) and it works very much like LSMW and it provides testing and logging functionality and is super fast.

If you follow the steps in customizing, it walks you through the process. Basically you first create a structure in the data dictionary that describes each line item you are going to post, then set up what type of postings you want and do the flat file to structure mappings, and off you go.

[Former Member]

Thanks Daniel,

Our requirements are to have custom output and email as well the requirement to post all records or rollback if any errors, which the BAPI and commit_work provides.

None the less, I looked at the program, configuration documentation, etc and will configuration/develop/prototype for evaluation purposes.

Meanwhile, do you know;

1) That the CO-PA planning framework(KEPM) needs to be configured in order for KEFC to work? We already have an Operation Concern setup but not the planning framework. I would assume the planning framework needs to be configured?

2) You mentioned “super fast”. Do you have a rough estimate on the number of records and the time it took to process the number of records? Obviously, the performance is dependent on a lot of factors but I want to get a rough estimate.

3) I assume that KEFC does not have the functionality of commit or rollback if any of the records have and error?

Thanks again for the good tip on KEFC.

Mike Vondran

eBay Inc.

[Former Member]

Hi Mike,

The main problem of FM *POSTDATA consist of that fact, that you have to execute COMMIT WORK AND WAIT!!! because you may lock plan data, if you are going to post data line by line. Alternatively, you need to analyze all data of your profitability concern y executing *GETDATA and then merge it in your data pool. Sometimes it becomes a dificult task.