cancel
Showing results for 
Search instead for 
Did you mean: 

Problem with Batch management - Activation is not working on EWM

markus_130974
Explorer
0 Kudos

Hello,

i have the following situation:

  • I connected an ECC 6 EHP3 to an decentralized EWM based on S4 1909.
  • I implemented the IDOC interface between this two systems.
  • Batch level on ERP system is on Plant level
  • I want to activate the batch management for a material (without stock in ECC and EWM) on ERP side and then transfer it with a MATMAS IDOC to the EWM system

I started the following sequence:

Activate batch management on ERP

Create the IDOC on ERP side with transaction BD87 - batch flag is inside the IDOC

IDOC is transferred to EWM system and processed successfully with code 53

When I check all the messages in the IDOC I saw the following messages

As a result of this MARC-XCHPF --> product is not set to batch managed.

Here ist the detail of the message

Can anybody help me what is going wrong here and what I can do to solve this issue.

Many thanks for your help

Kind regards

Markus

Accepted Solutions (0)

Answers (6)

Answers (6)

durendran_chandran
Participant
0 Kudos

Hi markus_130974,

I'm also facing this issue, you have any inputs for me, kindly share on how you resolved the issue.

Regards,

Durendran C

timrosezin
Explorer
0 Kudos

Hi,

I just ran into this specific problem too.

The solution: you need to maintain batch management requirement for the material in general (MARA-XCHPF) as well as for the plant specific material (MARC-XCHPF) in ECC before sending it to EWM.

You can actually see this in MM02 in EWM. The plant-specific batch requirement indicator becomes available only after you mark the batch requirement indicator for the material in general (and save):

Regards,

Tim

bhaskar_kandula
Discoverer
0 Kudos

Hi Markus,

Crosscheck the entries in table TCUCH for the Batch Definition.

Check the Batch Definition Status (Fields - KZDCH & KZDCH_OLD). Both fields should have values '0' - Batch unique at plant level.

Even though the Batch Definition in the SPRO is reflecting at Plant level, but the initial Batch definition value at Material level is stored in KZDCH_OLD field of TCUCH table and it causes inconsistencies.

Run the Batch Level Conversion Program available under SPRO-->Logistics-General-->Batch Management-->Specify Batch level and Activate Status Management-->Batch Level-> conversion.

Pass the plant in the selection screen and execute the report. This removes the inconsistencies.

Hope this should solve your problem.

Best Regards,

Bhaskar Kandula

markus_130974
Explorer
0 Kudos

Hello Markus,

yes I checked the relevant document and chapter and did exactly what is described with the converson rules. The status fields in MARA and MARC are filled with the good values. Nevertheless the error messages keeps the same on EWM - Field MARC-XCHPF is not ready for input.

What I did meanwhile is to change the batch level on EWM to client and manipulate the IDOC coming from ERP. I set the batch flag in the IDOC structure to MARA-XCHPF even is the batch level on ERP is on plant. This change is working on EWM and batch flag for material is set to active.

Do you have any further ideas?

Regards

Markus

former_member230160
Active Participant
0 Kudos

In addition please check if the batch level in EWM is the same as in ECC

If you changed the batch level you may also need to do a batch level conversion. I assume that you are still in a test system and this is no productive system.

The batch level conversion can be done in the customizing under Batch management - Specify Batch Level and Activate Status Management - Batch level -> conversion.

former_member230160
Active Participant
0 Kudos

Hello Markus,

did you check the "how to guide" for the integration that is attached to the note "2840129-Release information and restrictions of Decentralized EWM on S/4HANA 1909"?

There especially chapter 6.6 "converting data between sender and receiver". Check which value are passed in fields MARC-PSTAT and MARA-PSTAT / MARA-VPSTA

They control which "views" of the material are used.

Maybe also have a look at the following KBA note "2667914 - Updating of a field with transaction MM17 results in message MG140"

Best regards

Markus