General Description of the Feature
These feature deals with the design and development of a new concept, called Organization and Area Data, in DSW. The goal of this new functionality is to provide a solution to a complex matter introduced with the integration of DSW with SAP DMS.
The concept that is covered is that one customer (Business Partner) can have different values in the same set of fields (Area Data) per Organization. This provides the possibility to be able to have Offer and Orders for the same Business Partner that cover different Order, Shipping and Billing information.
GAP
In version 3.7.0 where this feature is included, there is a crucial GAP identified, related with the BP currency validation during the Lead creation process.
This GAP will be handled separately in a future version by the Feature RWZC-241 - Getting issue details... STATUS
Until this is handled, the field OCRD.Currency should be filled manually in newly created Business Partners with the Organization function, before the Lead creation.
If this is not filled, users will not able to select such BPs. The system will stop them with the warning message:
A. Area Data and Configuration
Divisions
A new administration page, called Divisions. is developed. Admin users can prepare Division entries which can be linked with existing Makes from the relevant Model Tree.
Each entry has:
- Presentation Code
- Description
- Make
The above fields are also exposed in the grid list as columns and can be reordered if it required.
Entries can be created, edited and deleted if it is required.
- URL: ~/UserManagement/DivisionsList
- Page BC: 12183
- Add/Edit BC: 12187
- Delete BC: 12188
When trying to delete a value, system is running a validation to ensure if the value is used on some Area Data:
Department - Distribution Channel
The once former Departments administration list has been redesigned to include the matrix for Distribution Channels. Each entry can be related with a specific Company and a Vehicle Status.
Each entry has the following fields:
- Code
- Name
- Company
- Car Status
Entries can be Created, Edited and Deleted:
- URL: ~/UserManagement/DepartmentsList
Company
Within the Company administration card page, two new tab are developed: Organizations, Areas
In the Organizations tab a list of all the available Organizations for this Company, along with their type, are displayed.
Through the Actions button, with the action "Add new Organization" an admin user can create new organizations for the relevant Company. An Organization entry can be Created, Edited and get Deleted through the row action of each entry.
- Add new Organization action & edit action >> BC: 12204
- Delete Organization action >> BC: 12205
Each entry has:
- Description
- Type: Sales/Purchase
* Note: Only "Sales" type is developed up to this version. - Active: Yes/No
* Note: An Active=No Organization is not displayed in all the relevant fields.
On delete action, system is running a validation to ensure if the selected value is used in existing Area Data:
In the Areas tab, a matrix of the combination between the above mention entities can be found and these consist the different Area Data.
Each Area data entry, is a matrix selection and includes the following fields in the grid list:
- Area Description
- Organization
- Division
- Distribution Channel
- Create Date
- Created By
- Update Date
- Updated By
Through the Actions button, with the action "Add new Area" an admin user can create new Area data matrix entry for the relevant Company. An Area entry can be Created, Edited and get Deleted through the row action of each entry.
- Add new Area action & edit action >> BC:12206
- Delete Area action >> BC: 12207
On delete action, system is running a validation to ensure if the selected value is used in existing Business Partner datasets:
User
In the User administration card page, a new tab is developed, called "User Organization". In this tab, Organizations per Company can be assigned to the relevant User to provide permissions to see/access Area data that belong to the assigned Organizations.
Through the Actions button, with the action "Assign User to Organization" an admin user can make such assignments.
In the list of the User Organization tab the following data are available:
- Company Description: based on the company the selected Organization is assigned to
- Organization Description: the description of the selected Organization
- Organization type: based on the type the selected Organization has
- Is Organization Active: based on the Active value the selected Organization has
A User Organization can be assigned to the User or get deleted:
- Assign User Organization action >> BC: 12189
- Delete User Organization action >> BC: 12208
B. Process
Business Partner
The Business Partner Edit and Creation page have been altered to introduce the new Area data information that are mandatory for this new process.
On Business Partner creation, a new section can be found under the general Contact data. This new section start with a filtering, where the user can select the Organization he is interested to add initial for this new Business Partner, and then cascading based on the previous selection to also select Division and Distribution Channel. After all the filtering selection a set of fields is displayed and these are the fields that can hold different data per Area selection.
The fields are:
| Section: Order |
|
| Section: Shipping |
|
| Section: Billing |
|
On Business Partner edit (after creation), the users are able to select the same Area Data filtering to preview or edit the values added in the fields or they can select a different set of Area Data filtering to add a different set of data to the mentioned fields. All these information can be found and edited in a new tab developed in the Business Partner card page, called "Area Data".
Actions
A new BP action, relevant with the Area Data, is developed. It is controlled by the BC: 12400 and called "Copy Area Data from".
With the use of this action, users are able to copy the current state of values from all the fields related to Area Data, from one Area to another. To do so, the user must perform the following steps:
- In the Area tab of a selected Business Partner, use the Area filters (Organization, Division, Distribution Channel) to select an Area that will be the destination of the copied data. This Area can have empty area fields or already some filled ones that will be overridden.
- From the Business Partner Actions, select the "Copy Area Data From"
- Select the Area (Organization, Division, Distribution Channel) that will act as the origin of the data.
- Save the action to perform the copy
The Area that was selected in the Area tab to be the destination, is filled with a copy of the relevant data.
Sales Lead
During the Sales Lead creation process and in the Lead creation pop-up, user are asked to select 3 new fields:
- Sales Organization
- Division
- Distribution Channel
The fields,
- include values based on the Organization permission of the User and the matrix available in the Areas of the company based on these Organizations.
- can be pre-filled, if the system manages to find an exact match, based on
- the User permission,
- Make of the VOI to relate with a Division
- Vehicle status of the VOI to relate with a Distribution Channel
A VOI created this way, is directly linked with selected Sales Area data and these are displayed in the Lead card page → Vehicle tab → line of the related Vehicle
A VOI can switch between Sales Areas using the row Action "Change Sales Area". A pop-up prompts the User to select a new set of Area data and on Save the VOI is transferred.
All the Offers created during on a Sales Area, are relevant to this sales area only. When the VOI is switched to a different Sales Area, users are able to see the previously created Offers, that belong to the other Sales Area, but they cannot use them to proceed to an Order.
During the Offer creation, system can validate that important BP information exist for the selected Sales Area. This validation can be triggered with two ways:
- Through a new WF validation "CheckForBpSalesAreaData" which can be configured in the Offer transition and informs the User about the existing of data.
- Through the regular "SimplySalesDocumentOfferView" required view, which triggers such validation before proceeding to the Offer page.
On the Order creation transition step, such validation can be repeated. It can be triggered, again, with two ways:
- Through a new WF validation "CheckForOfferExistanceInAreaAndBpSalesAreaData" which can be configured in the Order transition and informs the User about the existing of data. This validation, checks also, if there is already an Offer for the current VOI Sales Area data.
- Through the regular "Simple Sales Document Offer Accept View" required view, which triggers such validation before proceeding to the Offer preview and selection form.
The fields, from the Area data, that all the above mentioned validations check are:
- Account Assignment Group,
- Pricelist,
- Tax Classification,
- Currency
and the relevant message when the validation triggers is the following.
During the Order creation and after the validation, the Offer Preview and selection form is displayed. The users are able to see, select and view all the created Offer but they can select to transform to Order only the ones that are relevant with the current VOI Area data.
The rest of the Offer, do not provide any "Select" button in the preview form and they also include an info button. Upon opening the info button informs the user that this offer is not valid and cannot be selected because it belongs to a different Sales Area.
Integration
Using the mapping described in the configuration section, DSW and the DMS can communicate and exchange all the above mentioned Master and Transactional data including the selected Areas (Sales Area, Organization, Division, Distribution Channel), as well as all the new fields related with them.
The "Create/Update" API, as well as, the create/update Business Partner from DSW, jsons include a new section with all the above mentioned information. This means that we can receive from the DMS BPs with such info and also send to the DMS BPs with such info.
The same logic is followed from the Document creation. When an Offer or/and Order is created from DSW, along with the Document analysis, the new Area Data are included in the json of the API.
Business Partner json
Document json
Business Benefit
Incorporate and integrate the concept of Sales Areas in DSW. Business Partners can hold multiple values per field based on the Area Data and this can affect the created leads and Offers/Orders.
Configuration
Business Cases:
- Divisions (new admin page):
- Access the page BC: 12183
- "Add/Edit" action BC: 12187
- "Delete" action BC: 12188
- Organization (on the level of Company) - new tab
- Add new Organization action & edit action → BC: 12204
- Delete Organization action → BC: 12205
- Area (on the level of the Company) - new tab
- Add new Area action & edit action → BC:12206
- Delete Area action → BC: 12207
- User Organization (on the level of the User) - new tab
- Assign User Organization action → BC: 12189
- Delete User Organization action → BC: 12208
- Business Partner (action)
- 12400 - Copy Area Data from
Administration and Process pages:
- Divisions:
- URL: ~/UserManagement/DivisionsList
- Distribution Channel (existing page):
- URL: ~/UserManagement/DepartmentsList
- BP Area Data fields - source of values - Order
- Customer Group: ~/SetupEntities/List/Administration/IDMS_IndustrySector
- Currency: based on the active Currencies from ~/administration/currencies
- Pricelist: ~/item/PricelistsGridList
- BP Area Data fields - source of values - Shipping
- Branch: list of available Branches
- BP Area Data fields - source of values - Billing
- Payment Method: Payment Methods= ~/SetupEntities/PaymentTermsGridList
- Account Assignment Group: Financial Groups= ~/SetupEntities/FinancialGroupsGridListPage
- Tax Classification: VAT Business Groups= ~/SetupEntities/List/SalesAndLeads/IDMS_VATBUSGROUP
Option Fields:
- BP Area Data fields - source of values - Order
- Sales District: EntityName: BPAreaData - Field: SalesDistrict
- Sales Office: EntityName: BPAreaData - Field: SalesOffice
- Sales Group: EntityName: BPAreaData - Field: SalesGroup
- Price Group: EntityName: BPAreaData - Field: PriceGroup
- BP Area Data fields - source of values - Shipping
- Shipping Conditions: EntityName: BPAreaData - Field: ShippingCondition
Workflow:
Validations
- Offer related: CheckForBpSalesAreaData (checks that the group of mandatory fields and if they are filled with values in the relevant Sales Area)
- Order related: CheckForOfferExistanceInAreaAndBpSalesAreaData (checks if there is at least one Offer for the Sales Area assigned to the VOI and if the group of mandatory fields are filled with a value in this Sales Area on the BP)
Mapping:
- Relation: OneDealer to Integration Layer
- Mapping Objects:
- SalesArea
- Division
- Department
- Organization
- SalesDistrict
- SalesOffice
- SalesGroup
- ShippingCondition
Additional Information
New tables:
@IDMS_BP_SLSAREADATA:
| Name | Type | Comment |
|---|---|---|
| Code | NVARCHAR 50 | |
| Name | NVARCHAR 100 | |
| U_IDMS_BPCode | NVARCHAR 30 | OCRD.CardCode |
| U_IDMS_AreaCode | NVARCHAR 50 | IDMS_Area.Code |
| U_IDMS_SalesDistrict | NVARCHAR 50 | |
| U_IDMS_CustomerGroup | NVARCHAR 50 | |
| U_IDMS_SalesOffice | NVARCHAR 50 | |
| U_IDMS_SalesGroup | NVARCHAR 50 | |
| U_IDMS_ABCClass | NVARCHAR 254 | |
| U_IDMS_Currency | NVARCHAR 3 | OCRN.Code |
| U_IDMS_PriceGroup | NVARCHAR 50 | |
| U_IDMS_PriceList | INTEGER | PriceList.PriceListNo |
| U_IDMS_DeliveringPlant | NVARCHAR 30 | Branch.BranchID |
| U_IDMS_ShippingConditions | NVARCHAR 50 | |
| U_IDMS_PaymentTerms | NVARCHAR 50 | OCTG |
| U_IDMS_AccAssignmentGrp | NVARCHAR 50 | IDMS_FinancialGroup.Code |
| U_IDMS_TaxClassification | NVARCHAR 50 | VatBusinessGroup |
| U_IDMS_CreateDate | Timestamp | |
| U_IDMS_UpdateDate | Timestamp | |
| U_IDMS_CreatedBy | NVARCHAR 50 | USERLOGIN.ID |
| U_IDMS_UpdatedBy | NVARCHAR 50 | USERLOGIN.ID |
@IDMS_ORGANIZATION:
| Name | Type | Comment |
|---|---|---|
| Code | ||
| Name | ||
| U_IDMS_Description | ||
| U_IDMS_Type | Values: Purchase or Sales | |
| U_IDMS_Active | short 4 | |
| U_IDMS_CompanyID | nvarchar 50 | |
| U_IDMS_CreateDate | Timestamp | |
| U_IDMS_UpdateDate | Timestamp | |
| U_IDMS_CreatedBy | nvarchar 50 | USERLOGIN.ID |
| U_IDMS_UpdatedBy | nvarchar 50 | USERLOGIN.ID |
@IDMS_AREA:
| Name | Type | Comment |
|---|---|---|
| Code | NVARCHAR 50 | |
| Name | NVARCHAR 100 | |
| U_IDMS_Description | NVARCHAR 254 | |
| U_IDMS_OrganizationCode | NVARCHAR 50 | @IDMS_ORGANIZATION.Code |
| U_IDMS_DivisionCode | NVARCHAR 50 | @IDMS_DIVISION.Code |
| U_IDMS_DistrChannelCode | NVARCHAR 50 | @IDMS_DEPARTMENT.Code |
| U_IDMS_CreateDate | Timestamp | |
| U_IDMS_UpdateDate | Timestamp | |
| U_IDMS_CreatedBy | NVARCHAR 50 | USERLOGIN.ID |
| U_IDMS_UpdatedBy | NVARCHAR 50 | USERLOGIN.ID |
@IDMS_USERORG:
| Name | Type | Comment |
|---|---|---|
| Code | NVARCHAR 50 | |
| Name | NVARCHAR 100 | |
| U_IDMS_OrganizationCode | NVARCHAR 50 | @IDMS_ORGANIZATION.Code |
| U_IDMS_UserId | NVARCHAR 50 | USER.ID |
| U_IDMS_CreateDate | Timestamp | |
| U_IDMS_UpdateDate | Timestamp | |
| U_IDMS_CreatedBy | NVARCHAR 50 | USERLOGIN.ID |
| U_IDMS_UpdatedBy | NVARCHAR 50 | USERLOGIN.ID |
@IDMS_BP_SALESAREADATA:
| Name | Type | Comment |
|---|---|---|
| Code | ||
| Name | ||
| U_IDMS_AreaCode | NVARCHAR 50 | IDMS_Area.Code |
| U_IDMS_CreateDate | Timestamp | |
| U_IDMS_UpdateDate | Timestamp | |
| U_IDMS_CreatedBy | nvarchar 50 | USERLOGIN.ID |
| U_IDMS_UpdatedBy | nvarchar 50 | USERLOGIN.ID |
@IDMS_BP_PURCHAREADATA:
| Name | Type | Comment |
|---|---|---|
| Code | ||
| Name | ||
| U_IDMS_AreaCode | NVARCHAR 50 | IDMS_Area.Code |
| U_IDMS_CreateDate | Timestamp | |
| U_IDMS_UpdateDate | Timestamp | |
| U_IDMS_CreatedBy | nvarchar 50 | USERLOGIN.ID |
| U_IDMS_UpdatedBy | nvarchar 50 | USERLOGIN.ID |
@IDMS_DIVISION:
| Name | Type |
|---|---|
| Code | NVARCHAR 50 |
| Name | NVARCHAR 100 |
| U_IDMS_PresentationCode | NVARCHAR 50 |
| U_IDMS_Description | NVARCHAR 254 |
| U_IDMS_CreateDate | Timestamp |
| U_IDMS_UpdateDate | Timestamp |
| U_IDMS_CreatedBy | NVARCHAR 50 |
| U_IDMS_UpdatedBy | NVARCHAR 50 |
0 Comments