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
Tables used
The tables the program reads and updates. ECC and S/4HANA differences are marked separately.
| Table | Role | Access | System |
|---|---|---|---|
| CRHDWork Center Header | Loom = work center mapping and plant | Read | ECC + S/4 |
| AFKOOrder Header Data for PP Orders | Order header: release and planned quantity check | Read | ECC + S/4 |
| AFVCOperation within an Order | Operation and work center match, confirmation number | Read | ECC + S/4 |
| AFRUOrder Confirmations | Partial and final confirmations: metres, time, reason for variance | Write | ECC + S/4 |
| QMELNotification Header | Malfunction notification for long mechanical stops | Write | ECC + S/4 |
| BALHDRApplication Log Header | Interface run and error log | Write | ECC + 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
| Parameter | Description | Type | Reference field | Required | Example |
|---|---|---|---|---|---|
| S_WERKS | Plant | Range / multiple | CRHD-WERKS | Yes | 1000 |
| P_AGGR | Aggregation: hour / shift | Radio button | — | No | Saat |
| P_MINST | Minimum breakdown duration for a notification (min) | Single value | — | No | 30 |
| P_NOTIF | Open maintenance notifications for breakdowns | Checkbox | — | No | X |
| P_TEST | Test 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.
| # | Column | Target field | Required |
|---|---|---|---|
| 1 | Event ID | By rule Unique number assigned by the monitoring system | No |
| 2 | Loom (work center) | CRHD-ARBPL | Yes |
| 3 | Plant | CRHD-WERKS | Yes |
| 4 | Production order | AFKO-AUFNR | Yes |
| 5 | Operation | AFVC-VORNR | No |
| 6 | Event type | By rule Start, count, stop, resume or order end | No |
| 7 | Date | AFRU-ISDD | Yes |
| 8 | Start time | AFRU-ISDZ | Yes |
| 9 | End time | AFRU-IEDZ | No |
| 10 | Pick count | By rule Increase of the loom counter in the interval | No |
| 11 | Metres produced | AFRU-LMNGA | No |
| 12 | Stop reason | AFRU-GRUND | No |
Sample upload file
| 1 | Event ID | Loom (work center) * | Plant * | Production order * | Operation | Event type | Date * | Start time * | End time | Pick count | Metres produced | Stop reason |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2 | EV-240311 | DK-014 | 1000 | 1000452 | 0020 | Count | 11/16/2026 | 06:00 | 07:00 | 61,200 | 38.25 | |
| 3 | EV-240312 | DK-014 | 1000 | 1000452 | 0020 | Stop | 11/16/2026 | 07:12 | 07:51 | 0 | 0 | M01 |
| 4 | EV-240315 | DK-021 | 1000 | 1000467 | 0020 | Stop | 11/16/2026 | 09:05 | 09:11 | 0 | 0 | A02 |
| 5 | EV-240318 | DK-021 | 1000 | 1000467 | 0020 | Order end | 11/16/2026 | 13:00 | 13:40 | 8,400 | 5.25 |
Result list columns
| # | Column | Source |
|---|---|---|
| 1 | Event ID | Calculated ID of the incoming event |
| 2 | Loom | CRHD-ARBPL |
| 3 | Production order | AFRU-AUFNR |
| 4 | Operation | AFRU-VORNR |
| 5 | Metres confirmed | AFRU-LMNGA |
| 6 | Downtime (min) | Calculated Stop end − stop start |
| 7 | Efficiency % | Calculated Actual picks / (loom speed × minutes) × 100 |
| 8 | Confirmation number | AFRU-RUECK |
| 9 | Notification | QMEL-QMNUM |
| 10 | Status | Calculated Posted, skipped (duplicate) or error |
Sample result list
| Event ID | Loom | Production order | Operation | Metres confirmed | Downtime (min) | Efficiency % | Confirmation number | Notification | Status |
|---|---|---|---|---|---|---|---|---|---|
| EV-240311 | DK-014 | 1000452 | 0020 | 38.25 | 0 | 85 | 0000081244 | Posted | |
| EV-240312 | DK-014 | 1000452 | 0020 | 0 | 39 | 0 | 0000081244 | 10004518 | Posted, notification created |
| EV-240315 | DK-021 | 1000467 | 0020 | 0 | 6 | 0 | 0000081302 | Posted | |
| EV-240311 | DK-014 | 1000452 | 0020 | 0 | 0 | 0 | Skipped: event already processed |
How does the program work?
- 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.
- 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.
- 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.
- 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.
- 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.
- 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
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 …
Released Production Orders Without Any Confirmation Report
A custom ALV report that lists production orders that were released but have not received a confirmation for a single operation, with the days since …
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 …
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.