on ‎2025 Mar 07 5:21 PM
When we lock a Production version in ECC, it seems corresponding Production source header doesn't get invalid flag directly in IBP after CI-DS job is run. Is there any scenario where the flag will get set automatically in IBP after CI-DS integration or do we need to have it maintained manually?
Thanks
Request clarification before answering.
Hello Alok, you can address this issue by enhancing the load program and manipulating the validity dates.
Regards
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @alok_jaiswal,
Are you using the Supply Chain Integration Add-On for SAP IBP, in a Time-Series Based Planning Area? Do you mean, when the valid-to validity date of the Production Version is in the past, that you want to have the 'Production Source Invalid' Master Data attribute of the 'Production Source Header' Master Data Type populated with X (= invalid flag) in IBP?
Please inspect standard extractor /IBP/SOURCEPRODUCTION_ATTR, see also Solved: How to see the data in the Extractors of the Supply Chain Integration Add-On for SAP IBP?. In the extractor, you will notice it has the field PINVALID and you will notice that relevant rows are marked with X for this field. Regarding PINVALID, see also Integrating Data from SAP S/4HANA to SAP IBP Time-Series-Based Planning Areas > Master Data for Time....
What is needed for you is to, in CI-DS, map this PINVALID field of the Extractor to the 'Production Source Invalid' (= also has technical ID PINVALID in IBP) Master Data attribute of the 'Production Source Header' Master Data Type in IBP.
If you would also like to map 'deleted' records in S/4, please see the solution provided in Solved: Invalid Source Of Production - SAP Community.
Kind regards,
Vincent Verheyen
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Vincent,
Thanks for response and suggestion.
Yes, we are using Time series based planning area but not using standard extractors for now. We are getting data from standard tables like MKAL etc. We do filter out records via MKAL.MKSP!=1 so only valid records come over to IBP. However, for any existing records when PV is locked in ECC - those records are getting filtered out and therefore never come over to IBP and remains as valid in IBP. We can run the CI-DS task in REPLACE mode and that will sync both ECC & IBP systems - but that's comes with its own set of risks - like deletion of dependent planning objects, key figure data etc.
Also PV validity date is not changed - if its no longer relevant then it is just marked as locked in ECC.
So without using standard extractors is there any other approach to be explored? Maybe one thing we can try is to not use the MKAL.MKSP!=1 filter in the initial extract from ECC but use that to map PINVALID field in Production Source Header MDT where field is locked. Though this will approach will bring additional invalid records over to IBP.
Regards,
Alok
| User | Count |
|---|---|
| 14 | |
| 9 | |
| 8 | |
| 2 | |
| 2 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.