SAP IBP upload of co-products

[marco_ronsdorf]

Dear all,

we try to model co-production in SAP IBP SOP. Therefore, we modelled the scenario in Excel files and used the data integration app for upload.

During upload of SOURCEPRODUCTION MDT we received an error:

"Ambiguous value for non-root SOURCETYPE using root LOCID;SOURCEID at plan level XXXPA1.WKCOMPALTCOMPSRC in MD XXXSOURCEPRODUCTION."

The planning area is based on the unified planning area SAPIBP1. Main settings in SOURCEPRODUCTION:

.

Location ID* - Product ID* - Source ID* - Output Product Coefficient - Source Type

A ------------------- A1 --------------S1 ------------------1000 ------------------------ P

A --------------------A2 ------------- S1 -------------------100 ------------------------ C

.

Due to co-production the source type for the combination location-sourceid (A-S1) cannot be biunique, because for co-production the main product has the source type P and the co-product has source type C (for the same source ID).

I tried the solutions given bei OSS Note "2367185 - Master Data Load Error-Ambiguous value found for non-root attribute”, but removing attributes for planning level WKCOMPALTCOMPSRC does not work. The TS heuristic fails, because it expects the defined attributes.

Finally I removed key figure COMPONENTSUBSTCOSTRATE and planning level WKCOMPALCOMPSRC from the planning area. This fixes the issue with co-production.

I think this is a bug in the SAPIBP1 model - I checked 1905 and 1911, but for both the issue exists.

Any suggestions?

Thanks, Marco

[marco_ronsdorf]

Hi Arif,

this is the workaround I mentioned above.

Regards,

Marco

[marco_ronsdorf · Accepted solution]

SAPIBP1 configuration was wrong and will be corrected in future releases (not yet announced):

When modelling co-production the upload of master data type SOURCEPRODUCTION failed, because for the key LOCID, PRDID, SRCID the attribute SOURCETYPE has different values (P, C) on planning level WKCOMPALTCOMPSRC.

Attribute SOURCETYPE has to be removed from the planning level WKCOMPALTCOMPSRC in order to fix the issue..

After applying this change the upload of co-production master data went well.

[gomezw · Accepted solution]

Hi Marco,

Where you finally able to load the MD for this scenario?

Do you know when will it be corrected?

Best regards!

[Praveen_Jadhav]

Hi Marco,

Can you please check for Location ID & Source ID there is a unique source type. By the planning level configuration source type should be unique for Location ID | Source ID combination.

Regards,

Praveen

[marco_ronsdorf]

Hi Praveen,

this is what I mentioned initially: The same location id and source id are used for the main and the co-product, but both have different source types - the main product source type is P, co-product source type is C.

Location ID* - Product ID* - Source ID* - Output Product Coefficient - Source Type

A ------------------- A1 --------------S1 ------------------1000 ------------------------ P

A --------------------A2 ------------- S1 -------------------100 ------------------------ C

Regards,

Marco

[Praveen_Jadhav]

Hi Marco,

This is not an issue with the SAPIBP1 model but due to the data maintained the MDT XXXSOURCEPRODUCTION.

When the master data is empty, whatever data you load for the first time system allows you to load. but when you load the master data again or you load a key figure data which is related to planning level WKCOMPALTCOMPSRC, you get **Ambiguous** error.

Actually what system checks in the background is, for the root attributes present in the planning level all the other non-root attributes should be unique.

So in your case for root attribute Component Product ID, Substitute product id, Location ID, Source ID - there exist multiple combinations of non-root attributes.

Delete those entries and re-load the data. It will work.

P.S -- Check for the source type in MDT Source Production. I think for 1 combination of Location ID, Comp, Alt Comp & Source ID there is multiple source type.

Regards,

Praveen

[marco_ronsdorf]

Hi Praveen,

We do not model product substitution. Therefore, we do not have any values for Substitute product Ids.

Regards,

Marco