Ansicht
Dokumentation

BAPI_COSTACTPLN_READPRIMCOST - Primary Cost Planning: Read

BAPI_COSTACTPLN_READPRIMCOST - Primary Cost Planning: Read

SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   ABAP Short Reference  
This documentation is copyright by SAP AG.
SAP E-Book

Functionality

This method reads primary plan costs.

Example

You want to know which costs were planned for cost element 400000 on cost center 4210, cost center 4220, activity type 110, and on business process 1004210.

You can fill the tables as follows:

INDEXSTRUCTURE:

OBJECT_INDEX | VALUE_INDEX |

1 | 1 |

2 | 1 |

3 | 2 |

COOBJECT:

OBJECT_INDEX|COSTCENTER|ACTTYPE|ORDERID|WBS_ELEMENT|CO_BUSPROC

1 | 4210 | | | |

2 | 4220 | 110 | | |

3 | | | | | 1004210

TOTVALUE:

VALUE_INDEX|COST_ELEM|...

1 | 400000 |

2 | 400000 |

You do not need to specify TRANS_CURR if the field PLAN_CURRTYPE has been set to "C" (controlling area currency) or "O" (object currency) in HEADERINFO. If there are then data records for a cost element in different transaction currencies, the system returns a cumulated value as it does in manual planning. If you enter the transaction currency explicitly (PLAN_CURRTYPE = "T", TRANS_CURR filled), the system only returns data records with the specified transaction currency.

The records are then read accordingly. Note that the VALUE_INDEX field in the INDEXSTRUCTURE table must be filled uniquely in a different way from the write BAPIs. This means that each value may appear once only, so that the system can make a unique assignment of the values to be read to an object.

Notes





Parameters

CONTRL
COOBJECT
HEADERINFO
INDEXSTRUCTURE
PERVALUE
RETURN
TOTVALUE

Exceptions

Function Group

6026

SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by SAP AG.

Length: 2617 Date: 20240523 Time: 111630     sap01-206 ( 43 ms )