dspConduct
Post a Request Overview
A Role Processor with the Post role type posts a request to a target system after the Review role is finished.
When a Role Processor posts a request for the Post role, the request can be posted by:
- The Integrate process assigned to the scenario (used when posting to SAP). Refer to Add a Process to a Scenario for more information.
- Manual post. Refer to Use Manual Post for more information.
- A custom posting process developed for a target system.
NOTE: Custom posting pages or processes are created and maintained by users.
Posting takes place on theRequest Group Post and Request Post Process pages, which are automatically assigned to any role with the role type of Post.
A post can be posted individually or as a group post, which posts each process in priority order. The lowest priority is posted first.
A request moves to the Posting Started status when a Post role clicks the Post or Group Post icon on the Request Group Post and Request Post Process pages.
A request moves to the Posted with Errors status when all Integrate processes associated with the request are finished processing and at least one posting process has failed.
A request moves to the Posted status when all Integrate processes associated with the request are finished processing and all postings are successful.
NOTE: When a Request is created, each Integrate Process assigned to the Scenario is assigned a unique Posting ID which can be used to assist while troubleshooting. Integrate uses this Posting ID as a parameter for Integrate Process Template rules and validations. The Integrate Process is also passed a Where Clause used for the posting data views that only contains the Request ID (e.g. “WHERE RequestID = 999”).
NOTE: After a request is finished, the Post role can be finished, during which the Final Finish process runs. The data that was posted is downloaded into target tables. Refer to Finish a Role with the Post Role Type, and Register Tables for Download as a Finish Process in dspConduct™.
NOTE: A post can be posted multiple times. The messages related to posting failure or success on the Request Post Message page displays information about the latest post.
NOTE: A setting can be configured to automatically post a request. Refer to Auto Post a Request for more information.
NOTE: A dependent scenario may exist in another category. Refer to Allow a Scenario to be used in Other Categories for more information. When a business process uses a scenario from another category, the request that is created for that scenario will be created in the database/Webapp that is the default WebApp for that other category. For example, a category called Northwest Region has a default WebApp of NWRegion. It contains a scenario called Create SoldTo – General Data. This scenario has been configured for use in the category US Operations. A scenario in US Operations is Create SoldTo. A user could create a business process in the US Operations category that uses the Create SoldTo scenario as a parent of the Create SoldTo – General Data scenario from the Northwest Region category. When the business process is executed, a request is created in the NWRegion WebApp.
This section contains the following topics:
