Hi,
per default the technical DI API user entered in B1i SLD (default is B1i user) will not cause Events in the B1 event mechanism. This has been done to avoid looping.
Though the B1i user can be activated for B1 eventing, from my point of view the following option should be checked first.
1. Order Creation (Inbound: File, Outbound: B1)
2. Order Confirmation (Inbound: Internal Queue, Outbound: File)
Please combine both scenario step by using predecessor/successor.
In step one, you define your second step as successor, then the second step will be automatically started after step one is finished. Details can be found in B1i online help.
- Outbound Definition of step 1 (not possible for void outbound):
![Capture.PNG]()
- Inbound definition of step 2:
![Capture.PNG]()
You will get the DI result of step 1 available and can use the DocEntry information to retrieve the created Order details via B1 object call atom.
Best regards
Bastian
P.S.:
if you still want to activate B1i user for B1 events, please check "MAINTENANCE -> Cfg B1 Event Filter: B1i User Filter Switched On"
Check content help for details: 