1. The batch input on Transactions KB11, KB15, KB21, KB41 is still provided with the known function and restrictions from earlier one. There will be no enhancement for the profitability segment or for characteristics like funds, functions or grants or other enhancements which are made available with the new transactions KB11N, K21N, KB31N, KB41N, KB15N.
With 770004 and with reference to 860165, when you create batch input sessions, batch inputs can be run on the new transactions (KBxxN ).
2. The BAPI interfaces were enhanced, when compared with earlier one, so that they provide the same function as the corresponding online transactions. Next to the receiver objects specified in the BAPI documentation now profitability segments and user-defined fields can also be transferred to the interface.
- Profitability segments can be passed during the reposting of costs, revenues and with the activity allocations. When you repost costs or revenues, profitability segments can be used as senders or receivers of the costs, or revenues can be used as receivers only with activity allocations. The profitability segment is still transferred as a list of characteristics in tables SEND_CRITERIA or REC_CRITERIA to the BAPIs. SEND_CRITERIA is interpreted as a sender profitability segment and REC_CRITERIA as a receiver profitability segment. The field ITEMNO_ACC is used to link the entries in the tables SEND_CRITERIA or REC_CRITERIA to the rows of the table DOC_ITEMS.
For example, for a reposting of 10.00 EUR from a cost center to a profitability segment:
DOC_ITEMS:
SEND_CCTR = 0000121010
COST_ELEM = 0000400000
VALUE_TCUR = 10.00
TRANS_CURR = EUR
ITEMNO_ACC = 001
REC_CRITERIA:
ITEMNO_ACC = 001
FIELDNAME = BUKRS (company code)
CHARACTER = 0001
ITEMNO_ACC = 001
FIELDNAME = PRCTR (profit center)
CHARACTER = 0000111111
- The field names must correspond to the names of the components of the profitability segment in the DDIC structure COPACRIT.
- User-defined fields can be transferred as receivers of costs, revenues, activity allocations, manual cost allocations and statistical key figures. For the transfer of the corresponding information, the table CUSTOMER_FIELDS is added to the BAPI interface. The entries in this table must have the structure BAPICOBL_CI and are linked to the entries of the table DOC_ITEMS via line number ITEMNO_ACC, that is, related entries in the tables DOC_ITEMS and CUSTOMER_FIELDS must have the same number in the field ITEMNO_ACC.
3. For the transfer of actual data into Controlling a new top (Transaction Batchman) exists. This uses the above-listed BAPIs and supports the administration of messages which occur during the data transfer.
4. The reversal is now also possible by BAPI [BAPI_ACC_ACT_POSTINGS_REVERSE]. In this case, it is a negative posting, that is, the document to be reversed is read and reposted with opposite +/- signs.
See also CO -> CO-OM -> BAPIs for actual postings in Controlling (extended) and actual data transfer into Controlling (new).
Read Here at SAP ABAP Forum to Get Answers for More Questions like aforementioned.