Procurement & consumption of spare parts internally in Repair Process

[Siraj_Saibudeen]

Dear Experts,

I have a question related to internal procurement of spare parts from a centralised warehouse plant to the repair center plant, and consumption of the spare parts from the repair plant through a repair confirmation.

We have option to configure whether to create a material reservation or a Purchase Requisition for the spare parts logistics integration. If we choose PR, then a PR is created and we want to update that PR as a Stock Transfer Order with item category "U" to transfer the spare part from the central plant to the repair plant. The PR is converted to PO and the spare parts is transferred to the repair plant.

But how do we consume this spare part in the repair confirmation, because the standard movement types hardcoded are not used in this scenario. When we put in the actual spare parts quantity used as part of a repair, we want the system to consume the used parts from the repair plant. Is it possible through standard config or an enhancement is needed to accommodate this scenario.

If an enhancement is needed, what logic we should implement to fulfil this requirement. Any help or hints are highly appreciated!!

Thanks,

Siraj

[NicoG · Accepted solution]

Dear Siraj,

I assume your question is with regards to latest S/4HANA on-premise release. Do I understand your planned scenario correctly as described in the following steps (high-level)?

1. Create Service Order with Service Part Item.
2. Create purchase requisition (PR) from Service Part Item with PR Item Category “U” for STO for Stock Transfer from centralized warehouse to Repair Plant.
3. Logistics execution to do the transfer including Delivery, GI centralized warehouse, GR at Repair Plant.
4. Create Service Confirmation with reference to the Service Order Item and consume the part from Repair Plant when the Confirmation is completed.

If this understanding is correct, then my answer is that this is not yet possible in standard via configuration, but you could reach this via enhancement and eventually smaller modifications.

1. Register an own forward data class (like ZCL_CRMS4_PROC_SRVORDER_FWD) in this IMG activity for identifier SRVO and sequence 20. Your own class must use the standard class CL_CRMS4_PROC_SRVORDER_FWD as superclass.
   
   Transaction SPRO: Service => Transactions => Logistics Integration => Define Custom Handler Classes for Forward Data Exchange
   
2. Redefine the supermethod PREPARE_PURCHASE_REQ and maintained code to set the item category for the PR to U (fields: ls_pr_item-item_cat = ‘U’ + ls_pr_item_x_item_cat = ‘X’) and also you need to set the fields for the supplying plant and supplying storage location (fields: ls_pr_item-suppl_plnt, ls_pr_item_x-suppl_plnt, ls_pr_item-suppl_stloc, ls_pr_item_x-suppl_stloc ) as these are required if you create the STO. You need to know how you want to determine the supplying and receiving plant and storage location and implement it properly.
   Suppress the filling of the accounting object if you use account assignment, e.g. via internal order normally. Because in this case the GR posting including consumption would already be done during GR in the Repair Plant and not after completing the service confirmation.
   
3. Register an own forward data class (like ZCL_CRMS4_PROC_SRVCONF_FWD) in this IMG activity for identifier SRVC and sequence 10. Your own class must use the standard class CL_CRMS4_PROC_SRVCONF_FWD as superclass.
   
   Transaction SPRO: Service => Transactions => Logistics Integration => Define Custom Handler Classes for Forward Data Exchange
   
4. Redefine the supermethod FILL_GOODS_MOVEMENT and adjust the code so that the goods movement for this part item is not suppressed (which is normally done because in PR/PO scenario GR during PO processing is doing the consumption posting already. This is done base on the existence of a purchasing document which is also the case in the STO scenario).

Depending on your STO process, if you are using e.g. 1 or 2 step STO it could be possible that the document flow in the service order transaction history is not fully correct as this scenario is not yet supported by standard. In this case you have to check and eventually do enhancements/modifications to have the transaction history correct. Please check carefully during your test.

As the STO has no account assignment eventually posted transportation costs will not be booked directly to the accounting object of the service order item as there is no account assignment available in the STO. But all costs will be done from the goods movement posting of the service confirmation. You need to verify with your financial colleagues are ok with this scenario or if you have to adjust the process to fit all requirements.

I think that’s all I can provide and I hope it helps. Be aware that these are only Ideas for a customer specific implementation without any warranty or support.

Best regards

Nicolai

[Siraj_Saibudeen · Accepted solution]

Hi Nicolai,

This is exactly what I was looking for. Thanks a lot for your expert advice.

I will look into this in detail together with our development colleagues.

Thanks,

Siraj

[Siraj_Saibudeen · Accepted solution]

Hi nicolai.geier ,

We have implemented the above solution design you proposed, and it works like a charm. Of course we had some technical difficulties, but we managed to work around it and we have a working solution now.

I would like to thank you again for your expert advice and proposal. I also see that this design is included in the future roadmap, and hoping this will become part of the standard solution.

Thanks,

Siraj

[NicoG · Accepted solution]

Hi Siraj Saibudeen,

thanks for your nice feedback, happy that the proposal worked for you. Indeed, we delivered the proposed solution as a standard solution with the latest release 2023 FPS00 recently. The PR/PO item category "U" can now be set via a customizing setting in the logistic integration customizing as explained here:

https://help.sap.com/docs/SAP_S4HANA_ON-PREMISE/c9b5e9de6e674fb99fff88d72c352291/d5d9ce7c695a4cffbdc...

In case you implemented the BAdI CRM_SRV_SP_LOCATION for the plant/storage location (PL/SL) determination: This BAdI contains with release 2023 FPS00 a new import parameter IV_SUPPLYING in method IF_EX_CRM_SRV_SP_LOCATION~GET_SERVICE_MATERIAL_LOCATION. With this parameter you know if the PL/SL determination is called to determine the PL/SL (IV_SUPPLYING = X) or the receiving PL/SL (IV_SUPPLYING = initial). So the parameter IV_SUPPLYING is only filled in this new STO scenario with X if the system determines the supplying PL/SL, in all other cases the parameter is initial.

Best regards
Nicolai