on 04-16-2010 10:37 AM
Hi All,
We are having lot of CIF errors due to material status "40" in CIF, which restrict creation of P.reqs and PO at source location.
Eg:- LOC1 is a manufacturing location and LOC2 is a Distribution centre. A new Product A introduced at both location, having status status "40" at both the location.
When APO creates P.Reqs with source as LOC1 and Destination as LOC2 for this product, these p.reqs get stuck in CIF queue, as plant specific status "40" doesn't allow creation of P.Reqs at LOC1 in ECC.
We thought of creating a new status "Z1", which would allow the creation of P.Reqs and PO. But the requirement was to allow only creation of P.Reqs and not PO. But in the config setting in ECC for material status there is common setting for P.Reqs and PO and cannot be differentiated.
Have anybody come across such problem and whats the way to address this issue.
Thanks & Regards
Shankar
Hello Shankar,
Thank you very much.
BR,
Tiemin
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi All,
Thanks for your suggestion and help.
Just to let u know, the solution i have thought of to resolve this issue.
I will be using new material status in ECC, which will allow the creation of P.Reqs and PO and then use BADI during the creation of PO in ECC to check for this New status. If status is equal to NEW STATUS then don't allow to create the PO for the material and if not equal then allow the PO creation.
Many thanks & Regards
Shankar
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Shankar,
You may have to review the business process of setting the status 40 ( i.e. block pruchasing) for the materials for which you are ready to create purchase requisitions but not POs.
There are some customer exists in ERP for inbound processing, however, these may not help.
You will have to remove this status 40 for the products for which you expect to have PR created in APO. However, to check possibility to have configuration set up in ERP, such that, POs are not allowed to be created ( say by having a workflow or separate Purchase group).
I hope this gives some helpful ifnormation.
Regards
Datta
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Shankar,
I have never come across this. However, I would never send a material to SCM in the first place if I didn't want SCM to create Purchase reqs or purchase orders. Why not exclude these materials from your Core Interface Integration Models (set your MRP type to, say, ND rather than X0)..
Alternatively, try excluding these materials from your SCM Heuristics that are creating the orders.
Regards,
DB49.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Dogboy49,
Thanks for your reply.
We need to start the planning of these products in APO which are still not completely ready(costed) for all purpose( Status 60). Planners need it to plan for their meduim term capacity and raw materials requirement. Hence we cannot exclude it from APO.
Regards
Shankar
Shankar,
If the only issue were RM, then you could still exclude the parts, since SCM supports passing dependent rqments to APO even if the parent does not exist in SCM.
In your case, though, I would consider using one of the 'planning without assembly' planning strategies. Pass unconvertible planned orders from SCM to ERP rather than PRs/POs.
Rgds,
DB49
Hi Shankar,
Please check list of enahncements in SMOD transaction. The enhacements related to Purchase documents start with "CIFPUR.."
Or other path in SPRO is as below:
In the ERP system under Integration with Other SAP Components >> Advanced Planning and Optimization >> Application-Specific Settings and Enhancements >>Settings and Enhancements for External Procurement.
Because of the blocked status of the material ,while transferring the PR/PO data, the CIF prrogram -function call for creating the purchasing document does not get triggered. As written in earlier mail, the enhancement on SAP ECC inbound may not help, because, the material status is picked up from ECC ( or SAP R/3) material master data and not taken from APO.
Neverthless, you may please have a look at these enhancements.
I hope this gives insight to you.
Regards
Datta
Hi Datta and Shankar,
I agree that CIF UserExit on ECC side can't and shouldn't overrule the status check in ECC.
Since it's APO that creates PRs and the requirement was to allow only creation of P.Reqs and not PO,
I think you can use Exit APOCFPEP on APO side to send only PR and filter out PO.
On ECC side, no special status should be set for the material, as the result.
BR,
Tiemin
User | Count |
---|---|
7 | |
4 | |
3 | |
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.