PP Program Custom development Interface Textile and Apparel

Weaving Loom Monitoring (MES) Integration Interface: Confirmations, Downtime and Efficiency

Short answer: A custom interface that transfers order start, pick counter and downtime events from the loom monitoring system to SAP production orders automatically. Picks are converted to metres and posted as partial confirmations, stops are recorded with their reason code and long mechanical breakdowns open a maintenance notification; an efficiency rate is calculated for every loom.

Estimated effort
L · 12–18 working days
System
ECC and S/4HANA
Tables
6
Scope
Global · 1 industries
Built by
NeKuDos Teknoloji
Last updated

Why is the standard not enough?

CO11N and CO19 take confirmations manually or as time events; they do not convert the pick count from the loom counter into metres, do not classify stops by reason and do not open breakdown notifications. Confirmations typed in at shift end arrive late and downtime is lost. The interface transfers the data from its source, event by event and without duplicates.

Who uses it? Weaving production managers, shift supervisors, production planning and maintenance teams.

Closest standard alternatives

  • CO11N Single Screen Entry of Confirmations. Takes operation confirmations manually; no loom counter, metre conversion or downtime classification.
  • CO19 Enter Time Event. Takes start and end time events; does not convert picks into metres or open breakdown notifications.

Tables used

The tables the program reads and updates. ECC and S/4HANA differences are marked separately.

TableRoleAccessSystem
CRHDWork Center HeaderLoom = work center mapping and plantReadECC + S/4
AFKOOrder Header Data for PP OrdersOrder header: release and planned quantity checkReadECC + S/4
AFVCOperation within an OrderOperation and work center match, confirmation numberReadECC + S/4
AFRUOrder ConfirmationsPartial and final confirmations: metres, time, reason for varianceWriteECC + S/4
QMELNotification HeaderMalfunction notification for long mechanical stopsWriteECC + S/4
BALHDRApplication Log HeaderInterface run and error logWriteECC + S/4

BAPIs and functions used

  • BAPI_PRODORDCONF_CREATE_TTEnter Production Order Confirmation (Time Ticket). Posts the summed counter and downtime data as operation confirmations
  • BAPI_ALM_NOTIF_CREATECreate PM/CS Notification. Opens a maintenance notification on the loom equipment for long breakdowns
  • BAPI_TRANSACTION_COMMITCommit a BAPI transaction. Commits the work after each order group

Selection screen parameters

ParameterDescriptionTypeReference fieldRequiredExample
S_WERKSPlantRange / multipleCRHD-WERKSYes1000
P_AGGRAggregation: hour / shiftRadio button—NoSaat
P_MINSTMinimum breakdown duration for a notification (min)Single value—No30
P_NOTIFOpen maintenance notifications for breakdownsCheckbox—NoX
P_TESTTest mode (check without posting)Checkbox—No—

Input file columns

The columns of the upload template and the SAP fields they are written to. Columns with an asterisk are mandatory.

#ColumnTarget fieldRequired
1Event IDBy rule Unique number assigned by the monitoring systemNo
2Loom (work center)CRHD-ARBPLYes
3PlantCRHD-WERKSYes
4Production orderAFKO-AUFNRYes
5OperationAFVC-VORNRNo
6Event typeBy rule Start, count, stop, resume or order endNo
7DateAFRU-ISDDYes
8Start timeAFRU-ISDZYes
9End timeAFRU-IEDZNo
10Pick countBy rule Increase of the loom counter in the intervalNo
11Metres producedAFRU-LMNGANo
12Stop reasonAFRU-GRUNDNo

Sample upload file

1Event IDLoom (work center) *Plant *Production order *OperationEvent typeDate *Start time *End timePick countMetres producedStop reason
2EV-240311DK-014100010004520020Count11/16/202606:0007:0061,20038.25
3EV-240312DK-014100010004520020Stop11/16/202607:1207:5100M01
4EV-240315DK-021100010004670020Stop11/16/202609:0509:1100A02
5EV-240318DK-021100010004670020Order end11/16/202613:0013:408,4005.25
A view built with fictional sample data; not real system data.

Result list columns

#ColumnSource
1Event IDCalculated ID of the incoming event
2LoomCRHD-ARBPL
3Production orderAFRU-AUFNR
4OperationAFRU-VORNR
5Metres confirmedAFRU-LMNGA
6Downtime (min)Calculated Stop end − stop start
7Efficiency %Calculated Actual picks / (loom speed × minutes) × 100
8Confirmation numberAFRU-RUECK
9NotificationQMEL-QMNUM
10StatusCalculated Posted, skipped (duplicate) or error

Sample result list

Event IDLoomProduction orderOperationMetres confirmedDowntime (min)Efficiency %Confirmation numberNotificationStatus
EV-240311DK-0141000452002038.250850000081244Posted
EV-240312DK-014100045200200390000008124410004518Posted, notification created
EV-240315DK-021100046700200600000081302Posted
EV-240311DK-01410004520020000Skipped: event already processed
A view built with fictional sample data; not real system data.

How does the program work?

  1. The loom monitoring system sends events per loom (order start, hourly production counter, stop start/end, order end) by RFC, REST service or file. Every event carries a unique event ID; if the same ID arrives again it is skipped.
  2. The loom code is mapped to the work center in CRHD (ARBPL, WERKS). The production order and operation in the event are checked in AFKO/AFVC: the order must be released and the operation must be planned on that work center.
  3. Counter events are summed per hour or shift. The pick count is converted to metres with the quality’s weft density (picks/cm) and posted as a partial confirmation with BAPI_PRODORDCONF_CREATE_TT: the quantity goes to AFRU-LMNGA, the run time to the machine time activity (ISM01), and start and end to ISDD/ISDZ and IEDD/IEDZ.
  4. Stop events are classified by reason code (warp break, weft break, beam change, mechanical breakdown, no operator). Duration and reason are carried in the confirmation as the reason for variance (AFRU-GRUND). For mechanical breakdowns longer than the configured minutes, BAPI_ALM_NOTIF_CREATE opens a malfunction notification (QMEL) on the loom equipment.
  5. Efficiency = actual picks / (loom speed × total minutes), calculated per loom and shift. Results and errors are written to the application log (BALHDR) and shown on the monitoring screen.
  6. On the order end event the final confirmation flag (AFRU-AUERU) is set; if output is short of or above the planned quantity, the planner is informed.

Performance notes

Do not confirm every pick separately; sum events per hour or shift to keep the number of confirmations per order low. Buffer the loom-to-work-center and order-to-operation mapping at the start of the run. Queue events per order to avoid lock conflicts on the same order.

Features

  • Line-by-line result and error log The result of every event is shown in the application log and on the monitoring screen.
  • Test mode (check without posting)
  • Runs as a background job With file transfer it runs as a background job every few minutes.

Authorization objects

  • C_AFRU_AWKAuthorization to post confirmations by plant and order type
  • I_QMELAuthorization to create maintenance notifications by notification type

Frequently asked questions

Which loom monitoring systems does it work with?

It works with any system that can send events by REST service, RFC or file. During setup the event format and reason codes are mapped to that system; it does not depend on the loom brand.

Is a confirmation created for every pick?

No. Counter events are summed per hour or shift and one partial confirmation is posted per interval. This keeps the number of confirmations per order reasonable and the production reports readable.

Does it work on S/4HANA?

Yes. The confirmation and notification BAPIs are used the same way on S/4HANA; the AFRU and QMEL structures have not changed. Events can also be received through SAP Integration Suite.

Related reports

PP Program Custom Mass upload

Mass Production Order Confirmation Upload Program

A custom program that reads operation confirmations (yield, scrap, rework, activity times) coming from MES, shop-floor terminals or Excel at the end …

AFRU · AFKO · AFVC · AFFW

PP Report Custom ALV report

Scrap and Yield Analysis by Work Center Report

A custom ALV report that totals yield, scrap and rework from production confirmations per work center and operation, and compares the actual scrap …

AFRU · AFVC · AFVV · CRHD

Let us build this program for your system

Briefly describe your system and expectations. We will clarify the scope and come back with an effort and price quote.

Related report: Weaving Loom Monitoring (MES) Integration Interface: Confirmations, Downtime and Efficiency