|
Home | Financial Services Analytics | Financial Instruments Analytical Reference Data | Business Partner Event In | Create Views based on Business Partner Main Data Bulk Information |
Search |
||
Related Information |
||
| Where used | ||
ES Workplace Basket |
||
|
Open Basket
Add to Basket |
||
To create analytical views of business partners based on submitted information.
| Technical Name | FinancialInstrumentsAnalyticalReferenceDataBusinessPartnerEventIn.CreateViewsBasedOnBusinessPartnerMainDataBulkInfo |
| Namespace | http://sap.com/xi/BA/Global |
| Latest Software Component Version | FSAPPL 400 |
| First Shipped With: Software Component Version |
|
| First Shipped With: Product Version | BANKING SERVICES FROM SAP 7.0 - Banking Services from SAP 7.0 |
| Category | SAP A2A |
| Direction | inbound |
| Mode | asynchronous |
| Point-to-Point Communication Enabled |
|
| Release State | deprecated |
| Idempotency | not applicable |
| Business Function(s) required | Not Applicable
|
| Application Component for Customer Messages | FS-BP |
| WSDL |
The Create Views based on Business Partner Main Data Bulk Information inbound service operation creates analytical views of business partners based on Business Partner FS Main Data Bulk Information.
The Create Views based on Business Partner Main Data Bulk Information inbound service operation creates analytical views of business partner main data.
This service operation processes the BusinessPartnerFSMainDataBulkInformation message type.
The following information is required to create an analytical view of business partner main data:
The Create Views based on Business Partner Main Data Bulk Information and Create Views based on Business Partner Relationship Bulk Information service operations replace the Create Views based on Business Partner Bulk Information service operation.
When analytical views of business partners are created that are maintained in another system, we recommend aligning the Customizing for both systems. If mandatory fields or dependent objects are missing, processing of the particular business partner will fail.
For information about error handling in SAP Business Partner for Financial Services (SAP FS-BP), see Error Handling in banking services from SAP .
The Create Views based on Business Partner Main Data Bulk Information inbound service operation supports Error and Conflict Handling (ECH). The following error categories are used:
For more information about the individual error categories, see the code list for the global data type LogItemCategoryCode .
The BAdI: Determine ID of Bank Analyzer Business Partner Business Add-In (BAdI) is available for the Create Views based on Business Partner Main Data Bulk Information inbound service operation in Customizing for Financial Services under SAP Business Partner for Financial Services -> Settings for Financial Services -> Settings for Bank Analyzer -> Number Ranges and Groupings. For more information, see the BAdI documentation. This BAdI is called to determine the identifying attributes of the analytical view of the business partner, such as the:
A default implementation for this BAdI is provided.
The
BAdI: Determine Business Target Date
Business Add-In (BAdI) is available for the
Create Views based on Business Partner Main Data Bulk Information
inbound service operation in Customizing for Financial Services under SAP Business Partner for Financial Services -> Settings for Financial Services -> Settings for Bank Analyzer -> Versioning. For more information, see the BAdI documentation.
This BadI is called to determine the business date of the analytical view of the business partner. A default implementation for this BAdI is provided.
To use the
Create Views based on Business Partner Main Data Bulk Information
service operation, you must have implemented the SAP Business Partner for Financial Services (SAP FS-BP) application component and the related Customizing settings under Financial Services -> SAP Business Partner for Financial Services.
To ensure a correct version history of the analytical views of business partners created by the service operation Create Views based on Business Partner Main Data Bulk Information , the inbound data has to be processed or loaded daily. As a result, the process component that sends or provides the data based on which the analytical views of business partners are created, has to be scheduled at least every day.
In a scenario where the sending operation is the service operation Inform Business Partner Main Data as Bulk of the Business Partner Data Management process component, the corresponding agent has to be configured accordingly.
As analytical views of business partners are also created by the service operation Create Views based on Business Partner Relationship Bulk Information this also applies to this service operation.
If you are using the service operations Inform Business Partner Main Data as Bulk and Inform Business Partner Relationship as Bulk of the Business Partner Data Management process component, we recommend you schedule the agent corresponding to the service operation Inform Business Partner Main Data as Bulk before the agent corresponding to the service operation Inform Business Partner Relationship as Bulk .
If the Financial Instruments Analytical Reference Data process component and this service operation are temporarily unavailable and therefore daily processing of the service operation Create Views based on Business Partner Main Data Bulk Information is not possible, inbound processing or the messages have to be restarted sequentially for every single day rotating for the service operations Create Views based on Business Partner Main Data Bulk Information and Create Views based on Business Partner Relationship Bulk Information . This means that day A has to be processed for the service operations Create Views based on Business Partner Main Data Bulk Information and Create Views based on Business Partner Relationship Bulk Information before you can start processing day B (A < B).
If errors occur (technical errors or errors that require postprocessing) you need to resolve these before the next inbound processing for the affected business objects. Otherwise, manual corrections might be necessary.