Incident Number Subject

542317 / 2022 Labor on is possible when SFC is not in work

 Non BOM EWM component add request is failing in
542437 / 2022
queue monitor
363784 / 2022 GI not getting triggered to EWM Location
 BOM Version is not updated in shop order specific
457578 / 2022
Routing during LOIPRO processing
 By-Product receipt is allowing to receive more than the
417120 / 2022
planned quantity
 Repeated quality inspection for DC group created with
377634 / 2022
reference to In-Process Inspection lot from SAP ECC
 Inspection point-wise data collection where inspection
374217 / 2022
point shall be a user input.
417103 / 2022 Batch number input is required for By-Product
431370 / 2022 Unplanned By-Product receipt
 Backflush components displayed in the By-Product
417161 / 2022
receipt
417164 / 2022 Alternate component for By-Product
374061 / 2022 By-product receipt at EWM managed Storage Location
 Collect Work Time Popup is not appearing while Labor
393709 / 2022
Off

SAP JCo RFC Exception - error occurred during EWM

393791 / 2022
RFC message processing
 Details

Business Scenario:

Business requirement is to use a centralized POD where multiple operators will

labor on and labor off at an operation using the badge number.

Issue:

Operators can labor on before starting the SFC. Labor on shouldn’t be allowed, if
the SFC is not active.

Observation:

Standard behavior is allowing the operators to labor on to the SFCs with status In
Queue or In-work.

Attaching the Labor on to Start activity is not possible, because multiple users
need to labor on to the SFC.

Expectation:

Users should be allowed to labor on if the SFC is not active. There should be
some activity rule/setting where we can configure the behavior.

Why labor on is allowed when the SFC is not active? is this standard behavior? is
there any setting available to control this?
Business Scenario:

Business requirement is to assemble EWM managed non BOM component using

Standalone As-Built Configuration activity which should post the component
consumption to EWM.

Issue:

After adding the EWM managed non BOM component using Standalone As-
Built Configuration activity, the outbound message
ewmComponentAddReequest is failing in the queue monitor

Observation:

No component details are getting passed to the BAPI, the xslt is adding the
components if only they have the reservation number and reservation item
number.

As the non BOM component doesn’t have any reservation number its not passing
the components to BAPI, which is failing.

Please refer the attachment for details.

Expectation:

Business case is valid, Business needs to assemble the EWM managed non BOM
component, and the corresponding posting should be triggered to EWM.
Business requirement is to maintain the raw material/input material in EWM.
Finished and semifinished materials are getting received at IM location. Business
is adopting SAP MES. In MES assembly activity should trigger Goods issue from
EWM via ewmComponentAddRequest.

Issue:

ewmComponentAddRequest is not getting triggered upon Assembly.

Observation:

Finished/Semifinished goods production storage location (where GR get posted)

is IM managed where as Issue storage location of the BOM components are EMW
managed. When shop order is getting created at SAP ME after transferred from
SAP ECC, “Warehouse Number” in the “Main” tab at “Shop Order
Maintenance” Screen is not getting populated. As per standard ME field
mapping This field normally get populated by LOIPRO segment E1AFPOL –
LGNUM filed. E1AFPOL – LGNUM get value from Warehouse – storage location
mapping of the production storage location of the Order header material at SAP
ECC. In this case order header production storage location is IM managed, not
EWM managed.

Missing “Warehouse Number” at shop order header in SAP ME seems to be the

Business Scenario:

Business requirement is to use shop order specific Routing and BOM and in some
scenario business needs to change the BOM in ECC after releasing the Order to
ME.

Issue:

Change production activity is failing with exception “BOM is not assigned to the
routing please select a Routing to which BOM is assigned”

Observation:

Updated BOM Version is not updated in shop order specific Routing during
LOIPRO processing.

A new version of BOM is created due to the BOM change in ECC and no change
in the routing, but the BOM field in the Routing is pointing to the old version of
the routing.

Due to this unable to change the BOM in change production activity.

Please refer the attachment for details.

Expectation:

Business case is valid, Business needs to change only the BOM in ECC and need
to update the same in SAP ME using Change production.
Business Scenario:

Business requirement is to receive By-product only for the required quantity

defined in the BOM

Issue:

By-product receipt allows to receive more than the planned/required quantity.

It’s also not showing how much quantity have been already received for the By-
Product.

Observation:

By-Product receipt plugin is not validating the required quantity and there is no
rule to control this behavior.

By-Product receipt plugin is not showing the previously received By-product

details, for one By-Product it allowing to receive quantity multiple times.

Please refer the attachment for details.

Expectation:

Business case is valid, Business needs to restrict the receipt quantity and need to
see the received quantity of the By-Product.

please let us know if any workaround is available for this scenario.

Business Scenario:

Business requirement is to Integrate In-Process Inspection of SAP ECC to Data

collection in ME. Inspection lot is getting downloaded to SAP ME with LOIPRO
and creating DC groups and DC parameters. For a single SFC, business need to
collect data (Result recording in ECC) multiple time or repeated quality
inspection is required. In ECC the scenario has been managed by enabling free
inspection point at Routing.

Issue:

Standard ME doesn’t support multiple time data collection for a SFC at a

particular operation even after setting the “Allow Multiple Data Collection”
system rule to true. “Allow Multiple Data Collection” is working only for the DC
group getting created locally at ME.

As business shall be using order specific routing, it’ll be difficult to use

disposition function as after every order download, routing modification shall be
a cumbersome task.

Expectation:

SAP ME should allow repeated quality inspection for DC group created with
reference to in process inspection lot of ECC. Business case is valid.
Business Scenario:

Business requirement is to Integrate In-Process Inspection of SAP ECC to Data

collection in ME. Inspection lot is getting downloaded to SAP ME with LOIPRO
and creating DC groups and DC parameters. For a single SFC, business need to
collect data (Result recording in ECC) multiple time. In ECC the scenario has
been managed by enabling free inspection point at Routing.

Issue:

Standard ME doesn’t support Inspection point-wise data collection where

inspection point shall be a user input.

Expectation:

SAP ME should allow inspection point wise data collection. Business case is
valid.
Business Scenario:

Business requirement is to input batch number while receiving the by-product.

The By-product components having batch number requirement, which needs to

be collected in ME and transfer it to ECC.

Issue:

There is no option to collect the batch number while receiving the By-Product.

Observation:

By-Product receipt plugin is not considering the “Data to collect of Floor Stock
Receipt” value for the component.

Also, if we attach any mandatory field for the “Data to collect of Floor Stock
Receipt” the by-product receipt action is failing without any error in the screen,
but exception can be seen in the logs.

Please refer the attachment for details.

Expectation:

Business case is valid, need option to input batch number while receiving the By-
Product.
Business Scenario:

Business requirement is to receive unplanned by-product in EWM storage

location.

Raw materials are being received from the EWM, once the required components
are assembled, business needs to collect the leftovers as By-product, which is not
configured as By-Product in BOM.

Issue:

Standard SAP ME doesn’t support unplanned By-product receipt, like we can

assemble unplanned component to the SFC.

Observation:

Standalone By-Product receipt is not possible.

Expectation:

Business case is valid, please let us know if any workaround is available for this
scenario.
Business Scenario:

Business requirement is to receive by-products only for non backflushed

components.

While opening the By-Product receipt Plugin, need to hide the By-Products
which are configured as Backflush Components and show only the non
backflush items, otherwise operators will not know which By-Products needs to
be received manually.

Backflush By-Products will be handled in ECC upon operation confirmation.

Issue:

By-Product components which are configured as backflush components are

getting displayed in the By-Product receipt Plugin with input requirement

Observation:

By-Product receipt plugin is showing all the By-products irrespective of the

backflush indicator and it doesn’t have any option to show/hide backflush
components.

Please refer the attachment for details.

Expectation:

Business case is valid.please let us know if any workaround is available for this
scenario.
Business Scenario:

Business requirement is to receive alternate component for a by-product.

In the Business scenario business will be having leftover from any of the BOM
component and they want to receive that as By-Product, which is not configured
as By-Product in BOM.

In BOM a component is configured as By-Product, but instead of that that

component business want to receive any of the component from the alternate
component list.

Issue:

Standard SAP ME doesn’t support alternate component for By-product receipt,

like we can assemble alternate component to the SFC.

Observation:

Standalone By-Product receipt is not possible, By-Product plugin is not

considering the alternate components configured for the By-Product component.

Expectation:

Business case is valid, please let us know if any workaround is available for this
scenario,
Business Scenario:

Business requirement is to receive batch managed by-product in EWM storage

location

Issue:

Standard SAP ME doesn’t support By-product receipt at EWM managed Storage

Location

Observation:

In attachment

Expectation:

Business case is valid.

Business Scenario:

Business requirement is to use a centralized POD where multiple operators will

labor on and labor off using the badge number.

Issue:

Collect Work Time Popup is not appearing while Labor Off, due to this, operator
was unable enter the distributed activity times spent on the operation.

Observation:

The Collect Work Time Plugin is appearing only when the logged in user labor
off from the POD, when other users try to labor off, system is laboring off the
operator with out collecting the distributed activity times.

Expectation:

Collect Work Time Popup should appear to collect the distributed activity time
for all the operators, while Labor Off.

Business Scenario:

Business requirement is to maintain the raw material/input material in EWM.

Business is adopting SAP MES. In MES assembly activity should trigger Goods
issue from EWM via ewmComponentAddRequest.

Issue:

ewmComponentAddRequest is failing in MEINT Queue with error “Error

occurred during message processing”.

Observation:

Connection to the EWM is fine, we can execute JCo start session to the EWM
connection.

We are using the standard workflow and the JCo Interface is throwing Exception
while calling the RFC.

Expectation:

The standard workflow ewmComponentAddRequest should be processed

without any issue.
 Status Priority Component Name Component Description/Subproduct

Sent to SAP High MFG-ME-RPT Standard Reports

Sent to SAP High MFG-ME-PRD-GENProduct Genealogy
Sent to SAP High MFG-ME-INT Integration
In Processing by SAP High MFG-ME-PRD-GENProduct Genealogy
Confirmed High MFG-ME-PRD-DC Data Collection
Sent to SAP High MFG-ME-PRD-DC Data Collection
Confirmed High MFG-ME-PRD-DC Data Collection
Confirmed Medium MFG-ME-PRD-DC Data Collection
Confirmed Medium MFG-ME-PRD-DC Data Collection
Confirmed High MFG-ME-PRD-DC Data Collection
Confirmed Medium MFG-ME-PRD-DC Data Collection
Confirmed High MFG-ME-PRD-GENProduct Genealogy
Confirmed Automatically High MFG-ME-PRD-DC Data Collection

Confirmed High MFG-ME-INT Integration

Comment
Dear Customer,

Got the update from my developer colleagues that this one is an enhancement request
and has been added to the backlog list of enhancements with no promised
implementation date.

Best Regards,
Janos
SAP Product Support
Dear Soumya,

I had some further discussion on this with my developer colleagues and they have
confirmed that inspection points are not supported at all because it would require
changes in the basic design.

Best Regards,
Janos
SAP Product Support
Dear Customer,

Got the update from my developer colleagues that this one is an enhancement request
and has been added to the backlog list of enhancements with no promised
implementation date.

Best Regards,
Janos
SAP Product Support
Dear Customer,

Got the update from my developer colleagues that this one is an enhancement request
and has been added to the backlog list of enhancements with no promised
implementation date.

Best Regards,
Janos
SAP Product Support
Dear Customer,

Got the update from my developer colleagues that this one is an enhancement request
and has been added to the backlog list of enhancements with no promised
implementation date.

Best Regards,
Janos
SAP Product Support
Dear Customer,

Got the update from my developer colleagues that this one is an enhancement request
and has been added to the backlog list of enhancements with no promised
implementation date.

Best Regards,
Janos
SAP Product Support
Dear Customer,

Got the update from my developer colleagues that this one is an enhancement request
and has been added to the backlog list of enhancements with no promised
implementation date.

Best Regards,
Janos
SAP Product Support
No Solution Provided

It's strange that in MEINT, we need to specify the ECC logial system as eWM prgram ID
to get the things work