Why is my PO not transferring to E4H with risk management option checked off?

[prashant75]

Hello Experts,

We are implementing SAP Risk Management with E4H. It's getting newly implemented. While performing a test based on the instructions provided in the Implementation guide, I am running into a problem of PO not making to the E4H environment.

Things I have already done:

a. Activated MM0A in S4H

b. Activated Document transfer in S4H for the PO document type with Risk management and generate worklist option

c. Did all required configuration within E4H including but not limited to the following:

1. Under Gen Org structure setup: Defined plant BOM evaluation by assigning receiving plants to the Logical system. Defined X-plant BOM evaluation by assigning the receiving plants to the plant groups for a given logical system

2. Pref Mgmt Org structure setup: Defined Admin Units for Vendor Declaration and setting up the attributes like assigning plant group, assigning currency and exchange rate type, assigning numbering schemas, choosing calculation parameter for BOM explosion, and activating Product identifiers

3. Supplier's Declaration setup: Defined setup for LTSD with Goods retention period, valuation method, output communication options, Request for all suppliers checked, defined max calendar years, and request tolerance period, and defined reminder levels

4. Define Documents of Origin setup: Setup number ranges, Assign country groups, and activated combination of Admin unit & Doc of origin type for both inbound and outbound.

5. Output Management setup: Retained standard

d. Setup Admin unit as Master data in BP alongside an FTO for the company code in which the PO is generated and the LU for the receiving plant.

e. Transferred the Vendor and material from S4H to E4H

f. Distribute Agreement and Plant Assignments from E4H to S4H

Upon creating the PO and manually transferring to E4H with Compliance option, it goes through as normal but when I try sending with Risk management option, the system doesn't do anything.

Any help in this matter would help. I can provide screenshots too but the above steps are pretty standard for someone who knows GTS Preference management. 

Best, Prashant

[MOHAMMED_BASER]

Hi Prashant, is the GTS Plugin configuration done?

[soringherlan · Accepted solution]

Hi Prashant,

firstly, what the log in GTS say? You can check it with  /SAPSLL/PREVDI_01.

Have you checked also table /SAPSLL/PREPDOC? If yest what about field REQUEST_STATUS in this tabl?. I have the feeling is out of the validity range vs what you have maintained in the LTSD setting(e.g. request tolerance days vs the delivery date in your PO.) 

Regards,

[prashant75 · Accepted solution]

Hello there, With a bit of tinkering around the data, I now get an error that says "Documents for RIMA not transferred: see log in GTS". Upon trying to check SLG1 in GTS though, I don't see anything come through during the time I attempted to transfer the document. Also upon checking transfer log for Purchasing documents using txn: /SAPSLL/PREVDI_01 in E4H, there is no log data that exists.

I do see successful data interfacing for Compliance management but not for Risk management. 

I did check table /SAPSLL/PREPDOC and there aren't any entries there. As for your other question on the validity range, I have the request tolerance setup for 999 days and Delivery date on the PO is October 6, 2025

[soringherlan · Accepted solution]

Hi Prashant, this is the error typically you get when the configuration is wrong. I suggest reviewing step by step what is done. You can start with what you have defined in Define Cross Plant BOM evaluation as i have not saw bringing this customizing in discussion. and continue from there

[prashant75 · Accepted solution]

Thank you, @Soringherian. I updated the configuration steps in the Original question in red. Step f was the reason for PO failing to transfer from S4H to E4H. For the error "Documents for RIMA not transferred: see log in GTS", I had to check both Compliance and Risk check box before transferring PO from S4H to E4H.

[MOHAMMED_BASER]

Hi Prashant, you can troubleshoot going step by step as I have mentioned below.
1. Service Selection in Document Transfer
Ensure that the Risk Management service is explicitly selected during the PO transfer. In some cases, the system requires at least one service (Compliance, Customs, Risk) to be checked. If Risk is selected but not properly activated, the transfer may silently fail.

2. MM0A Configuration
Confirm that the MM0A entry includes Risk Management for the PO document type. Also verify that the Generate Worklist option is active for Risk.

3. LTSD Node – Legal Regulation Setup
Double-check that the Legal Regulation assigned to Risk Management is correctly mapped to the PO document type. Ensure that the Country Group assignment aligns with the vendor and plant locations involved in the PO.

4. Missing Determination of Preference Agreements
For Risk Management to trigger, preference agreements must be transferred from GTS to the feeder system.
This is a prerequisite for generating the worklist in GTS. Without it, the PO may not be flagged for Risk processing

5. No Logs in S4H
If no logs are captured during the transfer attempt, it may indicate missing activation of Initial Transfer of PO documents in S4H. Or missing GTS Plugin configuration. if so then
SPRO → SD → Foreign Trade/Customs → GTS Plug-in → Control Data for Transfer to SAP GTS → Technical Activation of Document Transfer

6. Check Customizing Table /SAPSLL/TLER3B
This table controls service activation. Ensure that the entry for apevs_r3 = MM0A includes Risk Management parameters.

Revisit the MM0A and LTSD configurations with a focus on Risk-specific flags. Check if the Risk Management service is greyed out or inactive during transfer — this often points to missing customizing entries. If possible, enable trace logs during the transfer to capture backend activity.
Consider running the PO transfer in debug mode or using transaction /SAPSLL/MM0A to validate service triggers.

Hope this will help you