Ansicht
Dokumentation

< ( RELNBBP_20B_WORKFLOW )

Addresses (Business Address Services)   Fill RESBD Structure from EBP Component Structure  
This documentation is copyright by SAP AG.

Short text

Changes to the SAP Business Workflow

Use

The following changes have been made to the SAP Business Workflow in Release 2.0B:

• A workflow wizard has been provided which assists you in defining your own workflow for approving shopping baskets.

• Two new standard user administration workflows are available

As of Release 2.0B it is no longer necessary to enter a password when creating or applying for a user ID in the SAP Business-to-Business Procurement system. Instead, the password is generated automatically by the system and sent to the employee requesting a user, via one of the following workflows:

• WS10000224: The password is generated and sent directly to the employee requesting the password by e-mail.

• WS10000223: The password is generated and sent via a work item to the administrator, who has to give approval. Once the approval process is complete, an e-mail is sent to the employee requesting a user. The e-mail contains either the password or information about why the application was turned down.
  

Errors that occur when the password is generated are displayed in the application monitors (see also Application Monitors).

• Approving managers can specify all subsequent approvers for the workflow at runtime when executing a work item for approval of a shopping basket.

• Approvers of the invoice workflow (WS10000211) are defined as follows:

• If the invoice is created by the vendor, it is approved by the creator of the requirement coverage request. If the creator cannot be determined, it is passed for approval to the adminstrator responsible. The administrator must be entered as a possible processor for the workflow task TS1008118.

• If the invoice is created by the employee, it is approved by the employee's manager.

• If the invoice is created by a professional purchaser, no approval is required.

• Evaluated Receipt Settlement does not require approval (see also Evaluated Receipt Settlement with Vendor)

After approval, the invoice is created in the SAP B2B Procurement system or in the backend system. If the invoice is rejected, an e-mail is sent to the contact person of the vendor. If the contact person cannot be determined, an e-mail is sent to the vendor address.

• The approvers of the confirmation workflow (WS10000197) are determined as follows:

• If the confirmation is created by the creator of the requirement coverage request, no approval is required.

• If the confirmation is created by the vendor or professional purchaser, it is approved by the creator of the requirement coverage request. If the creator cannot be determined, it is passed for approval to the administrator responsible. The administrator must be entered as a possible processor for the workflow task TS1008107.
  

After approval, the confirmation is created in the SAP B2B Procurement system or in the backend system. If the confirmation is rejected, an e-mail is sent to the contact person of the vendor. If the contact person cannot be determined, an e-mail is sent to the vendor address.

Effects on Existing Data

Effects on Data Transfer

Effects on System Administration

Effects on Customizing

Further Information

CPI1466 during Backup   BAL_S_LOG - Application Log: Log header data  
This documentation is copyright by SAP AG.

Length: 4372 Date: 20240603 Time: 163255     sap01-206 ( 68 ms )