Wondering if anyone can help with this.
We are using Posting Area 2640 in Social Billing to bill NCD entitlement items. Our implementation of the PSSCB_BILL_CREATE BAdI populates the PA2640_POS_ID* fields on the billing document items, which is then mapped to main / sub transactions by SAP standard code.
One of the keys to determine the main/ sub transaction is the benefit product ID (BENEFIT_ID_EXT field in PSSCD_NCDitem table). This is carried through from the SSP / GED / GPD and originally sourced from the PRODUCT_ID field in the COMM_PRODUCT master data table, which has a 40 character length. However the TFK033D table key fields used in Posting Area 2640 are defined as length 12, which is too short to hold the potential maximum product ID length.
Our options to make this work are:
- Modify the SAP standard TFK033D table and associated structures (which we would like to avoid if possible because other posting areas use this table as well and allowing 40 character data to be entered could cause unintended truncations)
- Limit our product IDs to 12 characters (which is not feasible due to the way they have been designed)
- Stop using Posting Area 2640 to do the mapping and implement our own custom mapping configuration table to go from benefit product to do main / sub transaction (however we would like to use as much SAP standard functionality as possible)
Any suggestions? How risky is it to modify the TFK033D table field length?