
Download Nonconformance File Attachments
You can use the Nonconformance(/api/nonconformance/nonconformances) API to get a list of IDs for files associated with logged nonconformances. Then, you can use the Nonconformance File Download API to retrieve these files one by one.
The Nonconformance File Download API provides the following endpoint:
GET /nonconformance/file/download
You can use this endpoint to retrieve files associated with logged nonconformances based on the file IDs.
Quality Inspection Enhancements
In a future release, we will separate the SFC completion in the Work Center POD and Operation Activity POD from the synchronization of inspection results to your integrated SAP ERP, SAP S/4HANA, and SAP S/4HANA Cloud system. After this function separation, choosing Complete in one of the two PODs when processing an SFC will only complete the SFC, but won't start the communication of inspection results to your integrated ERP system.
To synchronize inspection results to your integrated SAP ERP, SAP S/4HANA, and SAP S/4HANA Cloud system, you will then need to choose Submit Results.
As of release 2411, you can continue to synchronize inspection results back to your ERP system by choosing Complete or Submit Results in the Quality Inspection Characteristic List plugin in the Work Center POD or the Operation Activity POD.Badge ID, Badge User ID, and Badge User Name Variables when Configuring Production Process Action Types for PODs
You can use the Badge ID, Badge User ID, and Badge User Name variables for String and StringArray parameter types when you're configuring production process action types for your POD.
Change Production POD Plugin
You can now perform Change Production directly in PODs, using Change Production POD Plugin, to change a given SFC Routing and BOM.
OEE MDO in Manage Dashboards for Embedded SAC
The Manufacturing Data Object OEE has the following attributes that you can use for your analytics.
Attributes that represent duration in time are measured in "seconds".
AVAILABILITY | The ratio of the amount of time a resource was productive to the amount of time the resource was expected to be productive. |
BREAK_DURATION | Break time assigned for a shift. |
CREATED_AT | Date and time of creation of the record in OEE MDO in SAP Digital Manufacturing for execution |
LAST_UPDATED_AT | Date and time of last update of the record in OEE MDO in the database of SAP Digital Manufacturing for insights |
LOADING_TIME | Period of time during which a resource is expected to be available for production minus the scheduled production interruptions, such as maintenance stops, or shift breaks. |
NET_OPERATING_TIME | Amount of time required to produce the actual quantities (yield and scrap) based on the designed speed. It is calculated using the formula: Actual Quantities Produced (yield and scrap) x Standard Rate |
NET_PRODUCTION_TIME | Total Production Time minus downtimes that occurred during the Total Production Time. (Total Production Time - Downtime) |
OEE | Overall equipment effectiveness (= Availability x Performance x Quality) |
PERFORMANCE | The ratio of the amount of time needed to produce good and bad quality items to the amount of time that would have been needed to produce these items based on the designed speed. It is calculated using the formula: Performance = Net Operating Time / Net Production Time |
PLANT | Plant in which the OEE calculation is performed. |
QUALITY | The ratio of time needed to produce good quality products to the total number of quantities produced (yield and scrap). It is calculated using the formula: Value Operating Time / Net Operating Time. |
QUALITY_LOSS | The number of poor quality items (scrap) multiplied by the designed speed (standard rate). It is calculated using the formula: Quality Loss = (Actual Quantity - Quality Output) x Standard Rate |
RESOURCE | Resource for which the OEE calculation is performed. |
RUNNING_TIME | Loading time minus the amount of time that was lost because of unscheduled interruptions of the production |
SHIFT | Name or identifier of the defined shift. |
SHIFT_DURATION | Duration of the shift. |
SHIFT_END_DATETIME | The date/time when the shift ends. |
SHIFT_START_DATETIME | The date/time when the shift starts. |
SPEED_LOSS | Time that wasn't used for production because the actual production speed was slower than planned. It is calculated using the formula (Net Production Time - Net Operating Time). |
TOTAL_SCHEDULED_DOWN | Total amount of time allocated for scheduled or planned maintenance activities. |
TOTAL_UNSCHEDULDED_DOWN | Total amount of time for the unscheduled or unplanned interruptions. |
VALUE_OPERATING_TIME | The Value Operating Time is calculated by removing the quality loss from the Net Operating Time. Value Operating Time = Net Operating Time - Quality Loss |
WORKCENTER | Work center for which the OEE calculation is performed. |
The Component Consumption Reconciliation app allows you to review and correct failed component consumption transactions. You can use this app to ensure accurate inventory management and to complete component consumption transactions.
When you post a component for assembly, the inventory of the component is reduced in case of successful consumption. In the event of failure for a consumption request, the inventory isn't reduced, and the failed transactions are displayed in the Component Consumption Reconciliation app.
Key Features
Review and correct failed transactions.
Display the transaction status of a component in the Inventory Status Sync column.
Edit the records that are in failed sync status. The other records are in display only status.
Retry the transaction without making any change.
New persona-based Role Templates
Several new object-based and persona-based role templates are introduced, improving role granularity, including:
Check
For more details!
Anonymize User in Time Tracking
You can anonymize the time tracking user information using the Hide User Data functionality in the Manage Business Settings app.
Define MQTT Quality of Service (QoS)
The following three Quality of Service (QoS) levels enable network designers to make a choice between minimal data transmission and maximum reliability:
QoS 0 – This is for minimal data transmission. At this level, a message is sent just once to a subscriber, and no confirmation of receipt is sent back. Consequently, it’s impossible to tell whether subscribers have even received the message. This approach is also known as as fire and forget or at most once delivery. As this level simply assumes that a message has been delivered, messages that are to be delivered to disconnected clients that subsequently reconnect are not stored.
QoS 1 – The broker attempts to deliver a message to a subscriber and then waits for the subscriber to send back a confirmation that the message has been received. If the broker doesn’t receive such a confirmation within a certain time limit, it sends the message again. This method can result in the subscriber receiving the message multiple times if the broker doesn’t receive a confirmation from the subscriber in time. This is also referred to as at least once delivery.
QoS 2 – Both client and broker use a four-step handshake, ensuring that the message is received precisely once. This can also be described as exactly once delivery.
Line Monitor Shift Yield and Scrap POD Plugin
You can use this plugin to display an overview of yield and scrap information of a shift running multiple orders for the same material.
Shift Enhancements in Manage Resources and Manage Shifts
The Shift Assignment Calendar was added to the Shift Assignment tab in the Manage Resources app. The calendar has two views: two months and Gantt chart. The Shift to Resource Assignment browse was added to the Manage Shifts app to display all resources a shift is assigned to. The cross link allows you to quickly open the assigned resource.
Monitor Production Processes in SAP Cloud ALM
See What´s New for more.
Do you like this post? Please let me know in the comments section what you think. Any feedback is highly appreciated.
Or, if you have any questions, please check SAP Community Q&A Area, or comment down below.
Thanks,
Manoel Costa
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
5 | |
4 | |
4 | |
4 | |
3 | |
3 | |
3 | |
2 | |
2 | |
2 |