on 11-25-2015 3:50 PM
Dear Helpers,
I need some help! I try to set up an auto - assembly process.
Therefore I've activated at "Site Maintenance" the activity hook "auto assy components", I've setted up some components with entry "Data collect on assembly= NONE". After I've released a shop order, the AS-Build Summary Report hasn't shown auto assembled components.. okay, so my first thought was to complete the Operation where the auto assy Material is assigned to, but also after completing, no quantity or component was shown.
I thought maybe it is because of missing permissions for the site, so what I tried was to assign a Activity Group to the "auto assembly component" and I also setted up permissions to some User groups, but this wasn't helpful.
I also tried to put an activity hook "auto assy components" on its operations, also doesn't work.
Do you have some ideas where the problem is located? The Version of ME is 15.0.3.18
Thanks in advance for your help!!
Best Regards,
Marco
Hi Marco
Using the exact same version here, this hook works OK at operation level.
Did you "enable" the hook? It's easy to forget to do that. If it's on the site level, it should be on the POST_ORDER_RELEASE hook point - it will consume as soon as the order is released.
In your BOM definition, is the component assigned to an assembly operation too? If not, it won't assemble. Is the assembly data type overridden at BOM component level, by accident?
Stuart
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Do you have any exceptions in your NW log when you release the order?
If you have General Trace turned on via manufacturing-admin, you should see an entry like:
"in AutoAssembleComponentsHK.execute with inData...."
especially if you hook the activity on the operation (at PRE_START) and start the SFC.
Oh the log viewer is showing 4 error messages after shop release. May this is a topic for a developer?
Here they are -FYI-:
1.Error executing Job [name=QueueMessageCleaner,description=QueueMessageCleaner,filePath=Visiprise/ERPShopFloorIntegration/MessagePurging/MessageCleaner,enabled=true,state=SCHEDULED,nextruntime=Thu Nov 26 10:14:00 UTC 2015,cronTime=0 * * * * *,workerClassName=com.sap.xmii.scheduler.XacuteWorker,parameters={filepath=Visiprise/ERPShopFloorIntegration/MessagePurging/MessageCleaner, transaction=Visiprise/ERPShopFloorIntegration/MessagePurging/MessageCleaner, runAsUsername=MESYS, logLevel=ERROR, persistence=ONERROR, messageRetentionPeriod=24},created=2015-01-08 15:14:03.057,createdBy=MESYS,modified=null,modifiedBy= ,fileId=612]
2:Error executing Job [name=MessageEnqueuer,description=MessageEnqueuer,filePath=Visiprise/ERPShopFloorIntegration/SAPMEMessageEnqueuer/SAPMEMessageEnqueuingDispatcher,enabled=true,state=SCHEDULED,nextruntime=Thu Nov 26 10:14:00 UTC 2015,cronTime=0 * * * * *,workerClassName=com.sap.xmii.scheduler.XacuteWorker,parameters={filepath=Visiprise/ERPShopFloorIntegration/SAPMEMessageEnqueuer/SAPMEMessageEnqueuingDispatcher, transaction=Visiprise/ERPShopFloorIntegration/SAPMEMessageEnqueuer/SAPMEMessageEnqueuingDispatcher, runAsUsername=MESYS, logLevel=ERROR, persistence=ONERROR, numberOfMessages=200, deleteAfterQueuing=true},created=2015-01-08 15:14:01.48,createdBy=MESYS,modified=null,modifiedBy= ,fileId=615]
3:Error executing Job [name=InboundMessageEnqueuer,description=InboundMessageEnqueuer,filePath=Visiprise/ERPShopFloorIntegration/InboundEnqueuer/InboundEnqueuer,enabled=true,state=SCHEDULED,nextruntime=Thu Nov 26 10:14:00 UTC 2015,cronTime=0 * * * * *,workerClassName=com.sap.xmii.scheduler.XacuteWorker,parameters={filepath=Visiprise/ERPShopFloorIntegration/InboundEnqueuer/InboundEnqueuer, transaction=Visiprise/ERPShopFloorIntegration/InboundEnqueuer/InboundEnqueuer, runAsUsername=MESYS, logLevel=ERROR, persistence=ONERROR, numberOfMessages=200, serverName=XMIIIDOC01, deleteAfterEnqueuing=true, messageName=*},created=2015-01-08 15:14:04.513,createdBy=MESYS,modified=null,modifiedBy= ,fileId=606]
4:Error executing Job [name=MessageDispatcher,description=MessageDispatcher,filePath=Visiprise/ERPShopFloorIntegration/frame/dispatchers/simpleDispatcher/SimpleMessageDispatcher,enabled=true,state=SCHEDULED,nextruntime=Thu Nov 26 10:14:00 UTC 2015,cronTime=0 * * * * *,workerClassName=com.sap.xmii.scheduler.XacuteWorker,parameters={filepath=Visiprise/ERPShopFloorIntegration/frame/dispatchers/simpleDispatcher/SimpleMessageDispatcher, transaction=Visiprise/ERPShopFloorIntegration/frame/dispatchers/simpleDispatcher/SimpleMessageDispatcher, runAsUsername=MESYS, logLevel=ERROR, persistence=ONERROR, numberOfMessages=50},created=2015-01-08 15:14:00.09,createdBy=MESYS,modified=null,modifiedBy= ,fileId=658]
Ok, after I've activated a assy_Comp hook as prestart on the operation, the system is assembling those assy components.. Strange I've tried as pre complete and it wasn't working.. Okay I think this should solve the problem. Im a litlle bit confused why it's working now... But it works 🙂 Thx for your help!!
Hello Marco,
The hook can only be used at specific hook points - Auto Assemble Component - SAP Manufacturing Execution (SAP ME) - SAP Library
PRE_START
PRE_COMPLETE
POST_ORDER_RELEASE
PRE_COMPLETE should have worked for you.
Regards,
Konstantin
User | Count |
---|---|
85 | |
7 | |
6 | |
4 | |
3 | |
3 | |
3 | |
3 | |
3 | |
2 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.