Ansicht
Dokumentation

Status Management in Business Partner ( RELNCRM_20C_BP_STATUS )

Fill RESBD Structure from EBP Component Structure   CL_GUI_FRONTEND_SERVICES - Frontend Services  
This documentation is copyright by SAP AG.

Short text

Status Management in Business Partner

Use

As of Release 2.0C, general status management is introduced for CRM business partner.

In the standard release, the following statuses are available (system statuses) and can be set in business partner (BP) maintenance:

• Order block

• Delivery block

• Billing block

You can set these blocks as follows:

• Centrally

• Sales area-dependent

The sales area-dependent blocks are valid in addition to the central blocks. The status is indirectly set or reset when you enter or delete the blocking reason.

For the central block, the tab page Archiving/Blocking is used.
For all sales area-dependent blocks, the relevant tab pages for Sales, Shipping, or Billing are used.

For Release 3.0, there will also be system statuses that are set or reset by the archiving process (and not in BP maintenance):

• ARCR (archivable)

• DELA (archived)

• DELT (deleted)

For Release 2.0C, there is no corresponding status for the following central BP fields:

• Archiving flag

• Central block

• Business activity block

For Release 2.0C, as preparation for the archiving process, a business transaction check has already been introduced. It takes the system statuses, as well as the central BP fields, into account.

In Customizing for Status Management, you find the following business transactions:

• Change (CHAN)

If an archiving flag is set, a warning is given by the business transaction check.

For Release 3.0, if one of the archiving statuses is set, an error message will follow. You can display the business partner, but you cannot change it.

• Read (READ)

If an archiving flag is set (for Release 3.0A, also for the archiving process status), a warning is given. However, the business transaction is allowed.

Effects on Existing Data

Effects on Data Transfer

In the R/3 System, attributes are available that correspond to blocking reasons in CRM. Building up the new fields in CRM takes place with the help of the following XPRA reports:

• CRM_BUPA_MIGRATE_CBLOCKS

• CRM_BUPA_MIGRATE_SBLOCKS

The data tables, including Customizing, required for building up the new fields are transferred during initial download to CRM.

Effects on System Administration

Effects on Customizing

Common Customizing tables are used for central and sales area-dependent blocking reasons. The Customizing tables are used both in the R/3 System and in CRM, not only by business partner, but also for blocking application data (for example, orders).

In Customizing for Business Partners, in the activity Define Blocking Reasons of Status Management, make the necessary system settings in the IMG.

In addition to the existing system statuses, you can define your own user statuses.
To do this, make the necessary settings in the Customizing of the business transactions under Status Profile for User Status in the status management.

You can find the business transactions for the archiving process under Environment -> Transactions.

You can find the system status under Environment -> System Status.

Further Information

General Data in Customer Master   General Data in Customer Master  
This documentation is copyright by SAP AG.

Length: 4363 Date: 20240520 Time: 235016     sap01-206 ( 71 ms )