—

26 NO VEMB ER 2018 09 OC TOB ER 2018

AIM Ready Reckoner: SD & CRM

Contents
1.0 INDUSTRY USAGE.......................................................................................................................................................

2.0 CHANNEL......................................................................................................................................................................

3.0 APPLICATION...............................................................................................................................................................

4.0 VESSEL TYPE & CRANE...........................................................................................................................................

5.0 BUSINESS LINE..........................................................................................................................................................

6.0 SERVICE CATEGORY...............................................................................................................................................

7.0 AIM DIMENSIONS UPLOAD FOR SALES ORDERS & SERVICE ORDERS....................................................

8.0 AIM DIMENSIONS AT CUSTOMER MASTER......................................................................................................

9.0 AIM DIMENSIONS AT SALES ORG, ACCOUNT GROUP, & BU LEVEL..........................................................

10.0 Improvements in the AIM functionality – March 2018............................................................................................

11.0 Appendix......................................................................................................................................................................

1.0 INDUSTRY USAGE..............................................................................................................................................................

2.0 CHANNEL..............................................................................................................................................................................

3.0 APPLICATION......................................................................................................................................................................

4.0 VESSEL TYPE & CRANE.................................................................................................................................................

5.0 BUSINESS LINE..................................................................................................................................................................

6.0 SERVICE CATEGORY......................................................................................................................................................

7.0 AIM DIMENSIONS UPLOAD FOR SALES ORDERS & SERVICE ORDERS......................................................

8.0 AIM DIMENSIONS AT CUSTOMER MASTER...........................................................................................................

9.0 AIM DIMENSIONS AT SALES ORG, ACCOUNT GROUP & PG LEVEL.............................................................

1 /47
 A I M RE A DY RE CK O N E R: SD & CRM

Version History:

Version Change Description Author(s) Date

1.0 AIM Dimensions Design Document – initial draft Nagaraj G & Arijit Ghose 23.02.2016

2.0 ES 2016 BU inclusion; CRM details incorporated Nagaraj G & Arijit Ghose 29.02.2016
Sets Included in the Appendix, L2 of industry usage Nagaraj G & Arijit Ghose
13.06.2016
3.01.3 mandatory
L2 of industry usage mandatory & AIM Dimensions B R Ravindra
09.11.2016
4.0 mandatory for PG based on Validity Dates
B R Ravindra
ES 2017 Org. Structure changes 08.02.2017
5.0
B R Ravindra / Arijit 25.09.201815.10.
Addition of sections 7,8 & 9 & Appendix updated
6.0 2018
Improvements in the AIM design included – section Arijit
7.0 26.11.2018
10.0

2 /47
 A I M RE A DY RE CK O N E R: SD & CRM

AIM-ABB INFORMATION MANAGEMENT SYSTEM

AIM DIMENSIONS (AIM is a contraction of ABB Information Management System)

The following is a list of AIM dimensions used today in the ABB MIS of Sales and Service:

 Industry Usage
 Channel
 Application
 Vessel type and Crane
 Business Line
 Service Category

Dimensions in Detail

1.0 INDUSTRY USAGE

Industry Usage: To determine the usage of the Sales Order inOrder in various sectors of the applicable industries and
helps to determine the Key performance indicators per industry usage enabling a better visibility of the overall usage of
the delivery.

SD: Prerequisite:
 Applicable for Customers of Account Groups

 Third Parties Local (Local (Domestic) :): 2100

 Third Parties Foreign (Exports) :): 2300

 Sets usedSets used for Validation

 ZSDGL_APPL_GSBER_PREREQ : Applicable Business Area is maintained in the set

3 /47
 A I M RE A DY RE CK O N E R: SD & CRM

 ZSDGL_SOP_VKORG_PREREQ :PREREQ: Applicable Sales Organization is maintained in

the set
 ZSDGL_SOP_BSARK_PREREQ :PREREQ: Excluded PO types is maintained in the set

Note: All values maintained in these “sets” can be viewed in the Appendix below. Set maintenance is done via GS01/ GS02
/ GS03 transactions in the ECC system.

 Sales order types excluded for updating Industry Usage

 ZFSO :ZFSO: Service Spares Sales

 ZFSI : : Service Order Item
 ZCCM :ZCCM: CCM Order Type

 Industry Usage details ofdetails of Sales Order isOrder is maintained as per the usage hierarchy of 4
levels with Validitywith validity period in the table ZSDGL_SOINDUSTRY

Note: AIM Master Data maintenance is done via transaction ZSDGLAIMDM.

Logic:

Industry Usage can be updated if the conditions mentioned below are met 
 Account group 2100 & 2300
 Sales Organization to be maintained in the set
 Applicable for PO types not maintained in the set 
 Applicable only for the sales order other than ZFSO, ZFSI, ZCCM
 Only Industry Usage values maintained in the table ZSDGL_SOINDUSTRY can be used 
 

 Default Values for Industry usage and channel will be maintained in GIS and will be replicated to the
ECC Customer Master.

 While creating sale order for the given customer, these default values updated in the Customer master
would flow to Sale order, further business can retain these default values or can populate new values
from the available F4 selection list.

4 /47
 A I M RE A DY RE CK O N E R: SD & CRM

Customer Master Data:

CRM Prerequisite: Industry Usage

 Applicable for Customers of Account Groups

 Third Parties Local (Local (Domestic) : 2100

 Third Parties Foreign (Exports) :): 2300

 Custom Tables used for Validation


 ZCSGL_SALE_ORG: Applicable Sales Organization is maintained in the table


 Service order types Included for updating Industry Usage

 ZFSO :ZFSO: Service Spares Sales

5 /47
 A I M RE A DY RE CK O N E R: SD & CRM

 ZFSI : : Service Order Item

 ZCCM :ZCCM: CCM Order Type
 ZPRT :ZPRT: Project Service Order
 ZQPC :ZQPC: Service Quotation

 Industry Usage details aredetails maintainedare maintained as per the usage hierarchy withhierarchy
with Validity period in the table ZCSGL_SOINDUSTRY

Note: AIM Master Data maintenance is done via transaction ZCSGLAIMDM.

 Default values for Industry usage and channel maintained in ECC Customer master will be replicated
to CRM GIS table ZCSGL_CA_GIS_1 through a background job.

 While creating Service order for the given customer, these default values updated in the CRM GIS
table would flow to Service order, further business can retain these default values or can populate new
values from the available F4 selection list.

 All the AIM Dimensions are available under “Reporting Dimensions” block in CRM Service Orders.

UPDATE for both SD and CRM on the Industry Usage field:

As of April 2016April 2016, release, Industry usage Level 2 is mandatory in Sales and Service Orders

 This validation will ensure the user needs to enter an Industry Usage value of minimum Level 2 or more.

 This validation is controlled based on the required Sales Org with the activation date.
Table - ZSD_AIMLV_VALD and will be triggered at screen level of Additional tab B and at the time of
saving sales order.

6 /47
A I M RE A DY RE CK O N E R: SD & CRM

 Sales Organisation  Pre-requisite Sales org for AIM dimension level validation.
 AIM Field/Dimension  Pre-requisite AIM dimension for which level validation is applicable.
 Level  this will decide which level should be made mandatory for the given AIM dimension (values can
be 2, 3 etc).
 Min Fall back level example: for Industry usage Level 3 is mandatory, but not all the industry usage
values has level 3, some has only 2 levels, in this case, min fall back level defines which is the min level to
be maintained for the given AIM value.
 Deactivation indicator  to deactivate or make the table entry obsolete.

7 /47
 A I M RE A DY RE CK O N E R: SD & CRM

 This validation isn’t applicable for Old orders i.e. orders created prior to activation date against respective
sales Organisations.

 As applicable in case of other AIM validations, for orders created via interface this validation is not triggered.
i.e. interface orders can be saved without L2 value.

 However, for such interface sales orders if user manually navigates to “Additional tab B” in Change mode
(VA02), then the validation will be triggered.

T-code: ZCS_AIMLVL can be used to maintain the values against the AIM Dimensions in CRM

ZZSAPMV45A  Screen level coding for Additional Tab B

ZSDGL_HEADER_CHK_APPL This enhancement to be used for coding at the time of saving sales order

2.0 CHANNEL

Channel: Describes the way in which the goods are distributed to an end customer/user; updating the channel in system
helps us get Key performance indicator per channel enabling a better visibility for channel Management.

SD Prerequisite:

 Applicable for Customers of Account Groups

 Third Parties Local (Local (Domestic) : 2100

 Third Parties Foreign (Exports) :): 2300

 Sets usedSets used for Validation

 ZSDGL_SOP_VKORG_PREREQ (Applicable Sales Organization is maintained in the set)

 ZSDGL_SOP_BSARK_PREREQ (PO types to be excluded Is maintained in the set)

 Sales order types excluded for updating Channel

 ZFSO :ZFSO: Service Spares Sales

8 /47
 A I M RE A DY RE CK O N E R: SD & CRM

 ZFSI : : Service Order Item

 ZCCM :ZCCM: CCM Order Type

 Channel details ofdetails of deliverable is maintained as per the usage hierarchy of 2 levels with
Validitywith Validity period in the table ZSDGL_SOCHANNEL

Logic:

Channel can be updated if the conditions mentioned below are met 

 Account group and 2100 & 2300

 Sales Organization to be maintained in the set
 Applicable for PO types not maintained in the set 
 Applicable only for the sales order other than ZFSO, ZFSI ,ZFSI & ZCCM
 Only Industry Usage maintained in the table can be used 
 

Channel is updated in the customer master data as highlighted in the screen shot.

Customer Master Data:

Default channel value updated in the Sale order

9 /47
 A I M RE A DY RE CK O N E R: SD & CRM

CRM Prerequisite: Channel

 Applicable for Customers of Account Groups

 Third Parties Local (Local (Domestic) :): 2100

 Third Parties Foreign (Exports) :): 2300

 Custom Tables used for Validation

 ZCSGL_SALE_ORG: Applicable Sales Organization is maintained in the table



 Service order types Included for updating Channel

 ZFSO :ZFSO: Service Spares Sales

 ZFSI : : Service Order Item
 ZCCM :ZCCM: CCM Order Type
 ZPRT :ZPRT: Project Service Order
 ZQPC :ZQPC: Service Quotation

Channel details of deliverable is maintained as per the usage hierarchy with Validity period in the table
ZCSGL_SOCHANNEL

10 /47
 A I M RE A DY RE CK O N E R: SD & CRM

3.0 APPLICATION

Application: To analyze where exactly the deliverable is being used.

SD Prerequisite:

 Applicable for Customers of Account Groups

 Third Parties Local (Local (Domestic) : 2100

 Third Parties Foreign (Exports) :): 2300

 Sets usedSets used for Validation

 ZSDGL_SOP_VKORG_PREREQ_1 (Consists of applicable Sales Organizations)

 ZSDGL_APPL_GSBER_PREREQ (Consists of applicable Business units)
 ZSDGL_APPL_VSL_EXEMPT (Consists of PO types excluded)

 Sales order types excluded for updating Industry Application

 ZFSO :ZFSO: Service Spares Sales

 ZFSI : : Service Order Item
 ZCCM :ZCCM: CCM Order Type

 Table used for Validation

 ZSDGL_BU_VALID - Business Area/PG(s) for which AIM dimension maintained will be

mandatory for the validity period maintained in this Table.

T-code: ZSD_AIMVAL for maintenance of Entries.

 Table Structure:

 First column (ZZAIM_FIELD)  AIM dimension for which validity dates are applicable.
 Second column (GSBER)  Business Area pre-requisite for AIM Dimension i.e. AIM Dimension
will be mandatory for this Business Area/PG for the validity period maintained.
 Third column (ZZACT_DATE)  Activation Date from which AIM Dimension will be mandatory
for Business Area/PG maintained.
 Third column (ZZDEACT_DATE)  Deactivation date from which AIM Dimension will not be
mandatory for Business Area/PG maintained.

11 /47
 A I M RE A DY RE CK O N E R: SD & CRM

Logic:

Application field can be updated only if the condition mentioned below are satisfied:

 Applicable for Customers of Account Group 2100 & 2300

 Applicable for Business Areas maintained in the Set
 Not Applicable for the PO types maintained in the set
 Applicable for all Business Units but is Mandatory for BUs (RDMMG / RDMDR / RDMRO /RMSC/
DMPC/ PGGA/ PGGI/ PGGS/IAPG/IASC)
 In addition, the system checks whether there are validity dates maintained against the AIM Dimension for PG
in Table ZSDGL_BU_VALID, based on which the AIM Dimension will be mandatory.
 All entries Maintained in the table ZSDGL_APPL

CRM Prerequisite: Application

 Applicable for Customers of Account Groups

 Third Parties Local (Local (Domestic) :): 2100

 Third Parties Foreign (Exports) :): 2300

 Custom Tables used for Validation

 ZCSGL_APPL_AIM :AIM: BU Pre-Requisite

 ZCSGL_SORG_AIM4 :4: Applicable Sales Organization is maintained in the table

12 /47
A I M RE A DY RE CK O N E R: SD & CRM

 Table Structure:

 First column (SALES_ORG) Pre-requisite sales org for Application and V&C type
 Second column (BUL_ORG) Pre-requisite sales org for Business Line

 ZCSGL_APPL_AIM – Business Area/PG(s) for which Application is maintained in this table with
a validity period is maintained in this Table.


 Table Structure:

 First column (ZCS_DIVAP)  Business Area pre-requisite for application

 Second column (ZACTV_DATE)  Activation Date from which application will be mandatory
 Third column (ZDEACT_DATE1)  Deactivation date from which application will not be
mandatory

Note: If no dates are maintained against the Activation/Deactivation dates for a Business Area, in
such cases the application would be mandatory for transactions belonging to that BA irrespective of
when the transactions was created.

13 /47
 A I M RE A DY RE CK O N E R: SD & CRM

 Service order types Included for updating Application

 ZFSO :ZFSO: Service Spares Sales

 ZFSI : : Service Order Item
 ZCCM :ZCCM: CCM Order Type
 ZPRT :ZPRT: Project Service Order

 ZQPC :ZQPC: Service Quotation

Application master data are maintained as per the usage hierarchy with Validity period in the table ZCSGL_APPL.

ZCSGL_APPL
.

14 /47
 A I M RE A DY RE CK O N E R: SD & CRM

4.0 VESSEL TYPE & CRANE

SD Prerequisite:

 Applicable for Customers of Account Groups

 Third Parties Local (Local (Domestic) : 2100

 Third Parties Foreign (Exports) :): 2300

 Sets used for Validation

 ZSDGL_SOP_VKORG_PREREQ_1
 ZSDGL_APPL_VSL_EXEMPT
 ZSDGL_VESSL_GSBER_PREREQ

 Master Date Table

 ZSDGL_VESSELTY

 Sales order types excluded for updating Vessel Type and Crane

 ZFSO :ZFSO: Service Spares Sales

 ZFSI : : Service Order Item
 ZCCM :ZCCM: CCM Order Type

 Table used for Validation

 ZSDGL_BU_VALID - Business Area/PG(s) for which AIM dimension maintained will be

mandatory for the validity period maintained in this Table.

T-code: ZSD_AIMVAL for maintenance of Entries.

 Business Units
 PAMA
 PATU
 IATU
 IASC
 IAMP

Logic:
 Applicable for Customers of Account Group 2100 & 2300
 Applicable for Business Areas maintained in the Set
 Applicable for Business Units maintained in the set (PAMA/PATU/IATU/IASC/IAMP)
 In addition, the system checks whether there are validity dates maintained against the AIM Dimension for PG
in Table ZSDGL_BU_VALID, based on which the AIM Dimension will be mandatory.
 Applicable for Sales Organization maintained in the set
 Applicable for the PO types that are not maintained in the set.
 Not applicable for sales order types ZFSO/ZFSI/ZCCM
 Only Vessels maintained in the table ZSDGL_VESSELTY can be updated in the Sales order within the
validity period maintained

15 /47
 A I M RE A DY RE CK O N E R: SD & CRM

CRM Prerequisite: Vessel Type & Crane

 Applicable for Customers of Account Groups

 Third Parties Local (Local (Domestic) :): 2100

 Third Parties Foreign (Exports) :): 2300

 Custom Tables used for Validation

 ZCSGL_SORG_AIM4 :4: Applicable Sales Organization is maintained in the table

 ZCSGL_VSL_AIM: BU Pre-Requisite

 Table Structure:

 Column 1: VSL_DIV  BU pre-requisite for Vessel Type & Crane

 Column 2: BUL_DIV  BU pre-requisite for Business Line
 Column 3: VSL_ACTDA  Activation Date from which Vessel will be mandatory
 Column 4: BUL_ACTDA  Activation Date from which Business Line will be mandatory
 Column 5: VSL_DEACTDA  Deactivation date from which Vessel will not be mandatory
 Column 6: BUL_DEACTDA  Deactivation date from which Business Line will not be
mandatory

16 /47
 A I M RE A DY RE CK O N E R: SD & CRM

Service order types Included for updating Vessel Type and Crane

 ZFSO :ZFSO: Service Spares Sales

 ZFSI : : Service Order Item
 ZCCM :ZCCM: CCM Order Type
 ZPRT :ZPRT: Project Service Order
 ZQPC :ZQPC: Service Quotation

Vessel & Crane master values are maintained with Validity period in the table ZCSGL_VESSELTY.

5.0 BUSINESS LINE

Business Line:

Organization within a business unit responsible for selling a product, or customer solutions at all stages of the product
/Solution Life cycle, with this global classification we can get business line and thereby get a better visibility of the
organization within a Business Unit responsible for selling a product or product solution at all stages of the Product or
Solution Life cycle.

SD Prerequisite:

 Applicable for Customers of Account Groups

 Third Parties Local (Local (Domestic) : 2100

 Third Parties Foreign (Exports) :): 2300

 Sets used for Validation

 ZSDGL_BUS_VKORG_PREREQ
 ZSDGL_SOP_BSARK_PREREQ
 ZSDGL_ BUS_GSBER_PREREQ

 Master Data Table

 ZSDGL_SOBUSINESS

17 /47
 A I M RE A DY RE CK O N E R: SD & CRM

 Sales order types excluded for updating Industry Usage

 ZFSO :ZFSO: Service Spares Sales

 ZFSI : : Service Order Item
 ZCCM :ZCCM: CCM Order Type

 Table used for Validation

 ZSDGL_BU_VALID - Business Area/PG(s) for which AIM dimension maintained will be

mandatory for the validity period maintained in this Table.

T-code: ZSD_AIMVAL for maintenance of Entries.

 Applicable for Business Units

 DMRO
 DMMG
 PACT
 DMDR
 PAOG
 PGGA
 PGGI
 PGGS
 RMDR
 RMMG
 RMRO
 RMSC
 IAOG
 IAPG
 IACT

Logic:
 Applicable for Customers of Account Group 2100 & 2300
 Applicable for Business Areas maintained in the Set
 Applicable for Business Units maintained in the set
 In addition, the system checks whether there are validity dates maintained against the AIM Dimension for PG
in Table ZSDGL_BU_VALID, based on which the AIM Dimension will be mandatory.

 Applicable for Sales Organization maintained in the set
 Applicable for the PO types that are not maintained in the set.

18 /47
 A I M RE A DY RE CK O N E R: SD & CRM

 Not applicable for sales order types ZFSO/ZFSI/ZCCM

 Only Business lines maintained in the table ZSDGL_SOBUSINESS can be updated in the Sales order
within the validity period maintained

CRM Prerequisite: Business LineCRM Prerequisite: Business Line

 Applicable for Customers of Account Groups

 Third Parties Local (Local (Domestic) :): 2100

 Third Parties Foreign (Exports) :): 2300

 Custom Tables used for Validation

 ZCSGL_SORG_AIM4 :4: Applicable Sales Organization is maintained in the table

 ZCSGL_VSL_AIM: BU Pre-Requisite

 Table Structure:

 First column (ZZAIM_FIELD)  AIM dimension for which validity dates are applicable.
 Second column (GSBER)  Business Area pre-requisite for AIM Dimension i.e. AIM Dimension
will be mandatory for this Business Area/PG for the validity period maintained.
 Third column (ZZACT_DATE)  Activation Date from which AIM Dimension will be mandatory
for Business Area/PG maintained.
 Third column (ZZDEACT_DATE)  Deactivation date from which AIM Dimension will not be
mandatory for Business Area/PG maintained.



 Service order types Included for updating Industry Usage

 ZFSO :ZFSO: Service Spares Sales

 ZFSI : : Service Order Item
 ZCCM :ZCCM: CCM Order Type
 ZPRT :ZPRT: Project Service Order
 ZQPC :ZQPC: Service Quotation

Business Line master values are maintained with Validity period in the table ZCS_BULINE

19 /47
 A I M RE A DY RE CK O N E R: SD & CRM

6.0 SERVICE CATEGORY

Service Category: The Principle nature of service that is being sold.

SD Prerequisite:

 Tables used for Validation

 TVARVC
 Variable ZSDSRVCAT_ACTDATE ( With(With Sales Organization & Date )Date)

 Variable ZSDSRVCAT_TRTYPE ( Sales(Sales Order types excluded)

 ZSDSRVCAT_DEFAULT (Profit center wise default service category is maintained)

 ZSDGL_REPCAT (Report category validation with PRCTR)

 Sales order types excluded for updating Service Category

 ZFSO :ZFSO: Service Spares Sales

 ZFSI : : Service Order Item
 ZCCM :ZCCM: CCM Order Type
 ZCCR :ZCCR: NA
 ZCMR :ZCMR: NA
 ZINR :ZINR: ABB In-House Repair
 B1 : : Rebate Credit Memo Request
 B2 : : Rebate Correction Request
 B3 : : Part Rebate Settle Request
 B4 : : Reb.Req.f.Man.Accrls

 Service Category master data are maintained with Validity period in the table ZSD_SERVICE_CAT2




Logic:
 Applicable for all Customers of Account Groups
 Applicable for pProfit center maintained in the table ZSDGL_REPCAT
 Applicable for Sales Organization maintained in the TVARVC variable ZSDSRVCAT_ACTDATE
 Not applicable for sales order types maintained in the TVARVC variable ZSDSRVCAT_TRTYPE
 Only Service category values maintained in the table ZSD_SERVICE_CAT2 can be updated in the
Sales order within the validity period maintained

20 /47
 A I M RE A DY RE CK O N E R: SD & CRM

CRM Prerequisite: Service CategoryService Category

 Applicable for All Customers of Account Groups

 TVARVC variables used for the validation

 ZCSSRVCAT_ACTDATE :ACTDATE: Applicable Sales Organization with Activation Date

 ZCSSRVCAT_TRTYPE :TRTYPE: Applicable Service Order types

 ZFSO :ZFSO: Service Spares Sales
 ZFSI : : Service Order Item
 ZCCM :ZCCM: CCM Order Type
 ZPRT :ZPRT: Project Service Order
 ZQPC :ZQPC: Service Quotation
 ZCCR :ZCCR: Credit Memo Request
 ZCMR :CreditZCMR: Credit Memo Req-CCM
 ZSCU: Service Contract

 Service Category master data are maintained with Validity period in the table ZCSGL_SRVCATGRY

21 /47
 A I M RE A DY RE CK O N E R: SD & CRM

7.0 AIM DIMENSIONS UPLOAD FOR SALES ORDERS & SERVICE

ORDERS

All FE Data/AIM Dimensions viz. Industry Usage, Channel, Application, Business Line, Vessel Type, Service Category can be
uploaded at Sales Orders en-masse.

SD:

 Single upload program for all AIM dimensions. i.e. Industry Usage, Channel, Business line, Application,
Service category & Vessel Type via T-code: ZSD_AIMUPD.
 "validate file" option available to validate the upload entries.
 Excel based upload. If excel file has a value populated, then system will overwrite the original value with
value in excel file provided the value passes the validation.
 If excel file has a blank value against field, then system will not overwrite the original value and update only
those values populated in excel file for given order.
 Output log after upload is available to be future reference and actions.
 Foreground/background processing of upload allowed.
 If any field is non- mandatory and user wants it to be BLANK, identify the same by marking the field as $ in
excel file.
 Error is based on validation of each and every input field value. For example, if the four AIM dimensions are
right and two are wrong, the system will update the four correct AIM dimensions and throw error for the
wrong ones.

User Manual:

Logic:

 Upload of AIM Dimensions are allowed for sales document types based on entries in BRF + variable
ZSDGL_AIMUPD Source: Sales Org. (Ex:TH01) & Target: Sales document type (Ex: ZOR) though the PO
types corresponds to Interface order (Ex:CBOL, OMS etc) which were excluded for validation & upload
based on entries in sets ZSDGL_APPL_VSL_EXEMPT & ZSDGL_SOP_BSARK_PREREQ

CRM:

22 /47
 A I M RE A DY RE CK O N E R: SD & CRM

 AIM Dimension Upload program for Service orders - ZCS_AIMUPD.

 The link is available in the CRM Web UI as explained in the user manual.
 An option has been included to run it in "Validation only" mode so that you can receive a list of all potential
pre-run errors before you carry out the actual upload run; this gives you a chance to correct any errors in the
file before you do the actual upload.
 Further, provisions for detailed SLG1 logs have been included to provide complete visibility of the run-
results.
 The program can be run in both foreground and background, though background is recommended for larger
data volumes; however, in either mode, you can upload the file from your desktop local folder.
 The usual AIM dimension validations that kick in when you create the Service Order in real-time are also
built into the program: this ensures data correctness and consistency.

User Manual:

8.0 AIM DIMENSIONS AT CUSTOMER MASTER

All FE Data/AIM Dimensions viz. Industry Usage, Channel, Application, Business Line, Vessel Type, Service Category are now
available at Customer Sales area level.

 FE Data shall appear under the ‘Customer Master FE Data’ Tab.

 Visibility of the various FE Data can be controlled based on Account group at Sales area level (config).
 FE Data can be maintained while Customer is created/changed (XD01/XD02).
 All the Checks and controls available in Sales orders have been built in at Customer master Ex: Incorrect
entry, Obsolete entry, Level 2 validation etc.
 Intelligent Search-help (F4) built to filter the FE Data search based on the PG of the SAP Sales Division for
which the data is maintained (setting-dependent).
 Change logs are also generated for the customer master FE data changes.
 Sales Orders will default the FE Data from the Customer master if the values are maintained at the Sales area
level, Else system shall default the Industry Usage & Channel from the Customer master (which is the
current logic).
 Manual overwrites of the FE data in the sales order take precedence.
 Defaulting logic also applies to interface orders (OMS, CBOL, …).
 For SO >> SO copy, the original values in the SO will be copied over to the new SO, regardless of the
customer master sales area FE data values.

Logic:
 Applicable for Customers Account Groups maintained in TVARVC - YSDIN_CUST_AIM_KTOKD
 Applicable for Sales areas maintained in view cluster - ZSD_VC_AIM via SM34
 Screen activation can be carried at Sales area level from a given date – ZSD_VC_AIM (Table:
ZSD_CUST_AIM_CTL)
 Visibility of each field can be controlled at the Sales area level - ZSD_VC_AIM (Table:
ZSD_CUST_AIM_FCT)

 AIM Dimensions at Customer master sales area level is stored in Table: ZSD_CUSTOMER_AIM

AIM Dimensions at Customer master sales area level:

23 /47
 A I M RE A DY RE CK O N E R: SD & CRM

Upload Program for AIM Dimensions at Customer master Sales area level

 Mass upload of AIM Dimensions at customer master sales area level

 using T-code - ZSD_CUSFEUPD.
 Upload template can be downloaded from the T-code.
 File can be validated to check the upload records for correctness.
 All the Checks and controls available in Sales orders have been built in the upload program Ex: Incorrect
entry, Obsolete entry, Level 2 validation etc.
 Mass Uploads can be scheduled in Background, system also generates Application logs for future reference.
 Provision to update the FE Data for Blocked Customer available.

Upload Program:

24 /47
 A I M RE A DY RE CK O N E R: SD & CRM

User manual:

25 /47
 A I M RE A DY RE CK O N E R: SD & CRM

9.0 AIM DIMENSIONS AT SALES ORG, ACCOUNT GROUP, & BU & PG

LEVEL

All FE Data/AIM Dimensions viz. Industry Usage, Channel, Application, Business Line, Vessel Type, Service Category can now
be enabled at the Sales Organization, Account group & BUPG level.

 Visibility of the various AIM Dimensions can be controlled based on Sales Organization, Account group &
BUPG atin the Sales Transactions.
 AIM Dimensions applicable will be Optional in the Sales Transactions.
 AIM Dimensions such as Business line, Vessel & Crane will be visible only for applicable Product
groups(PGsBusiness Units (BUs).
 AIM Dimensions can be selectively enabled at the Product Group(PG)BU level.
 All the Existing checks and controls available in Sales orders Ex: Incorrect entry, Obsolete entry, Level 2
validation etc. are applicable.

Logic:
 Applicable for Sales Org, Customers Account Groups, AIM Dimension & product group(PG)Business Unit
(BU) combination maintained in Table - ZSDGL_AIM_DIMEN.

 Visibility of Business line & Vessel & Crane controlled based on the set mentioned in their respective
sections above.

AIM Dimensions in Sales Order belonging to 2900 account group customer:

26 /47
 A I M RE A DY RE CK O N E R: SD & CRM

10.0 Improvements in the AIM functionality – March 2018

Note: All examples cited below are meant for illustrative purposes only and bear no resemblance to actual FE data
values and validity dates.

1. FE Codes that have been discontinued are prompted with a new and self-explanatory error message, e.g.
Application AP.999 expired in Dec / 2017. The message text shows the date and month on which the code
expired. The user sees this message in Create or Edit SO if s/he mistakenly enters a code that is invalid on
the date of SO creation. This check applies to all six AIM dimensions in sales orders.

2. The above check applies to direct user entries only. If a value is selected via the F4, then valid values only
can be selected (this is an existing feature).

3. If the AIM code was valid at the time of SO creation, but is subsequently terminated by the Group, a
warning message with a new text is show to the user during subsequent SO changes, if the user navigates
to the Additional Data B tab. The same message-text (with month / year) as the above is flashed as a
warning so that user gets to know when the value has expired.

4. Direct junk value entries (i.e. without F4 selection) are now stopped with an error, e.g. Enter a valid
Service Category; this applies to all AIM dimensions. The said validation was already in place but we had
observed a few inconsistencies and bugs in the checks; the logic has been corrected now and the issue
resolved.

5. If descriptions are changed for the AIM master codes by the Group, our F4 dropdowns always show the
latest descriptions.

27 /47
 A I M RE A DY RE CK O N E R: SD & CRM

Illustration: if A.999 was called X in 2017, but Y in 2018, the F4 dropdown will always show Y making it
easier for the user to correlate these with the current values from the Group Master (previously, it was the
old description as of the SO creation date that was shown, and was sometimes confusing).

6. If FE values are subsequently extended to additional BUs, our F4 dropdowns show the latest domains
against each AIM code.

Illustration: if AP.888 was valid for EPPC only in 2017 but was extended to EPPC & RMDR in 2018, the
F4 dropdown will always show EPPC + RMDR, so that users can see the latest domains. Previously, it was
the domain list valid on the SO creation date that was shown.

7. Pts 5 and 6 apply in principle to hierarchical levels of AIM data as well, e.g. Level 2, and so on.

8. New FE / AIM values introduced subsequently are now shown in the F4 dropdown and available for
selection even for old open orders so that users can update old orders in change mode with new FE values,
if Business deems it appropriate. Sometimes, existing orders need to be re-categorized with new FE values
to achieve up-to-date and relevant reporting. This feature is completely new. Previously, only values valid
on the SO creation date were selectable and allowed; now, all current values are displayed in the F4. This
applies to all six AIM dimensions.

Illustration: SO created in Dec 2017 when user selected AP.777 in Application. A new code AP.888 was
introduced in 2018. When a user changes the SO in 2018, she can update AP.888 for Application if it is
appropriate; the system now allows AP.888 retrospectively, even though it did not exist at the time of SO
creation. AP.888 is available for selection via F4 as well as through direct entry.

9. In continuation of Pt 8 above, users can also enter new FE codes directly instead of navigating through the
dropdown: the system accepts new values valid on the current date.

10. Pt 8 applies in principle to hierarchical levels of AIM data as well, e.g. Level 2, and so on.

11. A brand-new optional feature has been introduced for countries to restrict their Application, Business
Line, Vessel & Crane selections to the values applicable to the anchor BU of the order. This has apparently
been a long-pending requirement and was not always so clearly defined. We have now launched a feature
whereby countries can have the F4 dropdown values filtered out and even restrict direct user entries as per
the BU of the order. To avoid impact on old and existing orders, this functionality can be activated from a
given date. SOs created on and from that date will be subject to the BU check, if this feature is switched on.

Countries who wish to leverage this functionality can raise a SOLMAN call; it’s a plug and play solution.
Business needs to tell us the sales organization, the dimension(s) they wish to control of the above three
(can be one, multiple, or all) and the date of activation. The document embedded below explains the
mechanics in more detail.

Illustration: if ZA switches on this check for ZA01 from 07 Mar 2018 for Application, then all ZA01 sales
orders created on or after 07 March will have the Application dropdown curtailed to show values specific to
the domain of the order. So, if AP.555 is valid for EPPC, it is not shown in the F4 and not available for
entry for an RMDR order. The BU of the first non-rejected item is considered as the anchor BU of the
order.

This feature can be activated for a sales organization + AIM dimension(s) + date. The three AIM
dimensions for which this feature currently applies are Application, Business Line, and Vessel and Crane.

28 /47
 A I M RE A DY RE CK O N E R: SD & CRM

12. In Pt 11, the domain checks usually apply to the above three dimensions only. By default, the values with
domain = ABB and domain = blank apply across domains and hence are always included in the F4
dropdowns and/or allowed for direct entry.

13. In continuation of Pt 11, if the BU check is activated, even direct user entries are validated and an error
message is shown if a user enters a code not valid for the BU in question, e.g. AP.777 not valid for BU
EPPC

14. Pt 11 in principle applies to hierarchical levels of AIM data as well, e.g. Level 2, and so on.

15. The AIM data mass upload program for sales orders (ZSD_AIMUPD) has been revamped and its features
made consistent with those of the other AIM upload program we recently developed for customers
(ZSD_CUSFEUPD). This has been done to facilitate a uniform user experience and ease of use.

The revised user manuals are attached below for your reference:

Mass Upload of AIM Dimensions in Sales Orders - ZSD_AIMUPD

Mass Upload of AIM Dimensions in Customer Masters - ZSD_CUSFEUPD

Note: Both programs store the upload results through SLG1 Application logs that are preserved for 30 days
after the program run. The user can refer to the logs and take remedial action for any failures.

29 /47
 A I M RE A DY RE CK O N E R: SD & CRM

11.0 AppendixPPENDIX:

Sets, custom tables, TVARVC & BRF+ used in the program for validation (SD):

For Application:

 ZSDGL_APPL_GSBER_PREREQ (BU Prerequisite for AIM – Appln)

 DMMG
 DMDR
 DMRO
 DMPC
 PGGI
 PGGA
 PGGS
 PAPG
 RMDR
 RMMG
 RMRO
 IAPG
 RMSC
 IASC
 ZCPG DMMG
 DMDR
 DMRO
 DMPC
 PGGA
 PGGI
 PGGS


 ZSDGL_APPL_VSL_EXEMPT (Application and Vessel Exempt Customer PO Types)

 B2B
 CBOL
 OCSB
 LSU
 OMS

 ZSDGL_SOP_VKORG_PREREQ_1 (1 Sales Org Prerequisite for AIM – Apn)

 IN01
 TH01
 AE01
 AE02
 AE03
 AE04

30 /47
 A I M RE A DY RE CK O N E R: SD & CRM

 AE05
 ID01
 PH01
 PH02
 VN01
 MY01
 APPL DMDR 31.12.2016  AU
01
DMM  SG
 APPL G 31.12.2016 01
 APPL DMPC 31.12.2016  NZ
 APPL DMRO 31.12.2016 01
 O
 APPL IAPG 01.01.2017 31.12.9999
M0
 APPL IASC 01.01.2017 31.12.9999 1
 APPL PAPG 01.04.2016 31.12.2016  QA
 APPL PGGA 01
 APPL PGGI  QA
02
 APPL PGGS  PK
 APPL RMDR 01.01.2017 31.12.9999 01
RMM  PK
 APPL G 01.01.2017 31.12.9999 02
 NG
 APPL RMRO 01.01.2017 31.12.9999
01
 APPL RMSC 01.01.2017 31.12.9999  NG
 BUS 02
L DMDR 31.12.2016
 ZSDGL_BU_VALID
 BUS DMM
(AIM Dimensions Mandatory against PG based on Validity Dates)
L G 31.12.2016
 BUS
L DMRO 31.12.2016
 BUS
L IACT 01.01.2017 31.12.9999
 BUS
L IAMP 01.07.2017 31.12.9999
 BUS
L IAOG 01.01.2017 31.12.9999
 BUS
L IAPG 01.01.2017 31.12.9999
 BUS
L IAPI 01.07.2017 31.12.9999
 BUS
L PACT 31.12.2016
 BUS
L PAOG 31.12.2016
 BUS
L PAPG 31.12.2016
 BUS
L PGGA
 BUS
L PGGI
 BUS
L PGGS
 BUS
L RMDR 01.01.2017 31.12.9999
 BUS RMM
L G 01.01.2017 31.12.9999
 BUS
L RMRO 01.01.2017 31.12.9999
 BUS
L RMSC 01.01.2017 31.12.9999
 VST
Y IAMP 01.01.2017 31.12.9999
 VST
Y IASC 01.01.2017 31.12.9999
 VST
Y IATU 01.01.2017 31.12.9999
 VST 31 /47
Y PAMA 31.12.2016
 VST
Y PATU 31.12.2016
 A I M RE A DY RE CK O N E R: SD & CRM

For Vessel Type & Crane:

 ZSDGL_SOP_VKORG_PREREQ_1 (SaleOrg Prerequisite for AIM – Appln/V&C)


 IN01
 SG01
 TH01
 NZ01
 AE01

32 /47
 A I M RE A DY RE CK O N E R: SD & CRM

 AE02
 AE03
 AE04
 AE05
 AU01
 VN01
 MY01
 ID01
 KW01
 PH01
 PH02
 SG08
 OM01
 QA01
 QA02
 ZA01
 PK01
 PK02
 NG01
 NG02
 MA01
 DZ01
 DZ02
 TN01
 TH06
 IQ01
 JO01
 JO02
 ID04
 EG01
 EG02
 EG03
 EG04
 EG05
 EG06
 NA01
 MU01
 MZ01
 TZ01
 KE01
 CI01
 CM01
 SN01
 ZM01

TH01
1. AE01
2. AE02
3. AE03
4. AE04
5. AE05
6. ID01
7. PH01
8. PH02
9. VN01
10. MY01
11. IN01

33 /47
 A I M RE A DY RE CK O N E R: SD & CRM

12. AU01
13. SG01
14. NZ01
15. OM01
16. QA01
17. QA02
18. ZA01

 ZSDGL_VESSL_GSBER_PREREQ (BU Prerequisite for AIM – V&C)

 PAMA
 PATU
 IAMP
 IATU
 IASC

 ZSDGL_APPL_VSL_EXEMPT (Application and Vessel Exempt PO Types)

 B2B
 CBOL
 OCSB
 LSU
 OMS

For Business Line:

 ZSDGL_BUS_VKORG_PREREQ (SaleOrg Prerequisite for AIM – BusinessLine)

 ZM01
 ZA01
 IN01
 AE01
 AE02
 AE03
 AE04
 AE05
 ID01
 PH01
 PH02
 TH01
 VN01
 MY02
 MY01
 AU01
 SG01
 KW01
 NZ01
 OM01
 QA01
 QA02
 PK01
 PK02
 NG01
 NG02
 AE01
 AE02
 AE03
 AE04
 AE05
 ID01

34 /47
 A I M RE A DY RE CK O N E R: SD & CRM

 IN01
 PH01
 PH02
 TH01
 VN01
 MY02
 MY01
 AU01
 SG01
 KW01
 NZ01
 OM01
 QA01
 QA02
 ZA01
 MA01
 DZ01
 DZ02
 TN01
 TH06
 IQ01
 JO01
 JO02
 ID04
 EG01
 EG02
 EG03
 EG04
 EG05
 EG06
 NA01
 CI01
 CM01
 SN01

 ZSDGL_ BUS_GSBER_PREREQ

 DMMG
 DMMG
 DMDR
 DMRO
 PACT
 PAOG
 PAPG
 PGGA
 PGGI
 PGGS
 RMDR
 RMMG
 RMRO
 RMSC
 IAOG
 IAPG
 IACT
 IAMP
 IAPI
 ZCPG

 ZSDGL_SOP_BSARK_PREREQ (PO Type - Exclusion in AIM)

 B2B
 LSU
 OCSB

35 /47
 A I M RE A DY RE CK O N E R: SD & CRM

 CBOL
 OMS
 DFUE

For Industry Usage:

 ZSDGL_SOP_VKORG_PREREQ (Sale Org Prerequisite for AIM Ind&us)

ZSDGL_APPL_GSBER_PREREQ ( Business Units Prerequisite for Aim Ind & Usg)

DMMG
DMDR
DMRO
DMPC
PGGI
PGGA
PGGS
PAPG

 SG01IN01
 SG01
 TH01
 NZ01
 AE01
 AE02
 AE03
 AE04
 AE05
 AU01
 VN01
 MY01
 ID01
 KW01
 PH01
 PH02
 SG08
 OM01
 QA01
 QA02
 ZA01
 PK01
 PK02
 NG01
 NG02
 MA01
 DZ01
 DZ02
 TN01
 TH06
 IQ01
 JO01
 JO02
 ID04
 EG01
 EG02
 EG03
 EG04
 EG05
 EG06
 NA01

36 /47
 A I M RE A DY RE CK O N E R: SD & CRM

 MU01
 MZ01
 TZ01
 KE01
 CI01
 CM01
 SN01
 ZM01
 IN01
 TH01
 NZ01
 AE01
 AE02
 AE03
 AE04
 AE05
 AU01
 VN01
 MY01
 ID01
 KW01
 PH01
 PH02
 SG08
 OM01
 QA01
 QA02
 ZA01
 ZM01

 ZSDGL_SOP_BSARK_PREREQ (PO Type - Exclusion in AIM)

 B2B
 LSU
 OCSB
 CBOL
 OMS
 DFUE

 ZSD_AIMLV_VALD (AIM Dimension – Mandatory Level Validation)

 AU01 ZZINDUSAGE1 19.05.2016 2 INDUSTRY USAGE

37 /47
 A I M RE A DY RE CK O N E R: SD & CRM

 CI01 ZZINDUSAGE1 15.01.2018 2 INDUSTRY USAGE

 CM01 ZZINDUSAGE1 15.01.2018 2 INDUSTRY USAGE
 ID04 ZZINDUSAGE1 01.01.2016 2 INDUSTRY USAGE
 IN01 ZZINDUSAGE1 19.04.2016 2 INDUSTRY USAGE
 MY01 ZZINDUSAGE1 19.04.2016 2 INDUSTRY USAGE
 NZ01 ZZINDUSAGE1 19.04.2016 2 INDUSTRY USAGE
 OM01 ZZINDUSAGE1 19.04.2016 2 INDUSTRY USAGE
 PH01 ZZINDUSAGE1 26.07.2016 2 INDUSTRY USAGE
 QA01 ZZINDUSAGE1 19.04.2016 2 INDUSTRY USAGE
 QA02 ZZINDUSAGE1 19.04.2016 2 INDUSTRY USAGE
 SG01 ZZINDUSAGE1 01.01.2016 2 INDUSTRY USAGE
 SG08 ZZINDUSAGE1 01.01.2016 2 INDUSTRY USAGE
 SN01 ZZINDUSAGE1 15.01.2018 2 INDUSTRY USAGE
 TH01 ZZINDUSAGE1 19.04.2016 2 INDUSTRY USAGE
 VN01 ZZINDUSAGE1 19.04.2016 2 INDUSTRY USAGE
 ZA01 ZZINDUSAGE1 25.07.2016 2 INDUSTRY USAGE
 ZA01 ZZSRVCAT 01.11.2017 2 SERVICE CATEGORY


For Channel:

 ZSD_AIMLV_VALD (AIM Dimension – Mandatory Level Validation)

•

 IN01
 SG01
 TH01
 NZ01
 AE01
 AE02
 AE03
 AE04
 AE05
 AU01
 VN01
 MY01
 ID01
 KW01
 PH01
 PH02
 SG08
 OM01
 QA01
 QA02
 ZA01
 PK01
 PK02
 NG01
 NG02
 MA01
 DZ01
 DZ02
 TN01
 TH06
 IQ01
 JO01
 JO02
 ID04
 EG01
 EG02
 EG03

38 /47
 A I M RE A DY RE CK O N E R: SD & CRM

 EG04
 EG05
 EG06
 NA01
 MU01
 MZ01
 TZ01
 KE01
 CI01
 CM01
 SN01
 ZM01

 ZSDGL_SOP_BSARK_PREREQ (PO Type - Exclusion in AIM)

• NA01
SG01
TH01
NZ01
AE01
AE02
AE03
AE04
AE05
AU01
VN01
MY01
ID01
KW01
PH01
PH02
SG08
OM01
QA01
QA02
PK01
PK02

 B2B
 LSU
 OCSB
 CBOL
 OMS
 DFUE

For Service Category:

 ZSDSRVCAT_ACTDATE (TVARVC Variable - Activation against Sales Org)

 IN01 03.04.2015
 KW01 03.04.2015
 MY01 03.04.2015
 NZ01 03.04.2015
 NZ02 03.04.2015
 OM01 03.04.2015
 PH01 03.04.2015
 QA01 03.04.2015
 QA02 03.04.2015
 SG01 03.04.2015

39 /47
 A I M RE A DY RE CK O N E R: SD & CRM

 SG08 03.04.2015
 TH01 03.04.2015
 VN01 03.04.2015
 PK01 30.12.2015
 PK02 30.12.2015
 ZA01 08.01.2016
 MA01 01.10.2016
 DZ01 01.10.2016
 DZ02 01.10.2016
 TN01 01.10.2016
 TH06 01.01.2017
 ID04 18.01.2017
 EG01 11.04.2017
 EG02 11.04.2017
 EG03 11.04.2017
 EG04 11.04.2017
 EG05 11.04.2017
 EG06 11.04.2017
 IN05 30.12.2017
 CI01 13.01.2018
 CM01 13.01.2018
 SN01 13.01.2018
 ZM01 24.09.2018


 ZSDSRVCAT_TRTYPE (TVARVC Variable - Sales Order types excluded)




 ZFSO
 ZFSI
 ZCCM
 ZCCR
 ZCMR
 ZINR
 B1
 B2
 B3
 B4

 ZSDRVCAT_DEFAULT (TVARVC Variable -Default Service category against Profit Center)

 AU40135 S12
 AU20135 S12
 AU30135 S12
 AU60135 S12
 AU90135 S12
 AU90138 S12
 SG10291 S12
 SG11133 S12
 SG11265 S12
 SG80154S12
 SG13251 S55
 SG80106S65
 SG80107S65
 SG81106S65
 AU30715 S12
 AU90106 S57
 AU90146 S57
 SG10236S12

40 /47
 A I M RE A DY RE CK O N E R: SD & CRM

AIM Dimensions at Customer master sales area

 Screen Control

 Field Control

AIM Dimensions at Sales Org, Account grp & PG level

 AE01 2500 ZZBUSINESS

 AE01 2500 ZZCHANNEL
 AE01 2500 ZZINDUSAGE1
 AE01 2500 ZZSITE_ID
 AE01 2600 ZZBUSINESS
 AE01 2600 ZZCHANNEL
 AE01 2600 ZZINDUSAGE1
 AE01 2600 ZZSITE_ID
 AE02 2500 ZZBUSINESS
 AE02 2500 ZZCHANNEL
 AE02 2500 ZZINDUSAGE1
 AE02 2500 ZZSITE_ID
 AE02 2600 ZZBUSINESS
 AE02 2600 ZZCHANNEL
 AE02 2600 ZZINDUSAGE1
 AE02 2600 ZZSITE_ID
 AE02 2900 ZZBUSINESS
 AE02 2900 ZZCHANNEL
 AE02 2900 ZZINDUSAGE1
 AE02 2900 ZZSITE_ID
 AE04 2500 ZZBUSINESS
 AE04 2500 ZZCHANNEL
 AE04 2500 ZZINDUSAGE1
 AE04 2500 ZZSITE_ID
 AE04 2600 ZZBUSINESS
 AE04 2600 ZZCHANNEL
 AE04 2600 ZZINDUSAGE1
 AE04 2600 ZZSITE_ID
 AE04 2900 ZZBUSINESS
 AE04 2900 ZZCHANNEL
 AE04 2900 ZZINDUSAGE1
 AE04 2900 ZZSITE_ID

Additional settings were added for IN-IAPI on 15 Oct 2018:

41 /47
 A I M RE A DY RE CK O N E R: SD & CRM

1. ZSD_SO_FLD_VALID: configured as warning message (entries attached in excel). The settings will throw a
warning message if Business Line is not filled in for the IAPI orders for IN.

2. ZSDGL_AIM_DIMEN: enabled Business line field for 2500 and 2600 account groups for IAPI (refer screen
shot below). This configuration enables the Business Line field for 25* and 26* customer account groups so that
the field is opened up in sales orders for Business to key in.

Custom tables & TVARVCs used in the program for validation (CRM):

42 /47
 A I M RE A DY RE CK O N E R: SD & CRM

For Industry Usage & Channel:

 ZCSGL_SALE_ORG (Sales Org Pre-requisites)

 O 50000609O 50000519
 O 50000609
 O 50000611
 O 50000829
 O 50000968
 O 50000983
 O 50001060
 O 50001073
 O 50001181
 O 50001461
 O 50001616
 O 50001755
 O 50001757
 O 50001774
 O 50002056
 O 50007583
 O 50007584
 O 50007585
 O 50007586
 O 50007587
 O 50000611
 O 50000829
 O 50000968
 O 50000983
 O 50001060
 O 50001073
 O 50001181
 O 50001616
 O 50001755
 O 50001757
 O 50001774
 O 50002056
 O 50007583
 O 50007584
 O 50007585
 O 50007586
O 50007587
 ZCSGL_AIMLV_VALD (AIM Dimension – Mandatory Level Validation)

 O 50000519 ZZCUSTOMER_H1001 19.04.2016 2 Industry Usage

 O 50000829 ZZCUSTOMER_H1001 19.04.2016 2 Industry Usage
 O 50000968 ZZCUSTOMER_H1001 19.05.2016 2 Industry Usage
 O 50000983 ZZCUSTOMER_H1001 01.01.2016 2 Industry Usage
 O 50001073 ZZBUISNESSLINE 01.02.2017 2 Business Line
 O 50001073 ZZCUSTOMER_H1001 19.04.2016 2 Industry Usage
 O 50001073 ZZCUSTOMER_H1002 01.02.2017 2 Channel
 O 50001073 ZZCUSTOMER_H1004 01.02.2017 2 Service Category
 O 50001461 ZZCUSTOMER_H1001 19.04.2016 2 Industry Usage
 O 50001616 ZZCUSTOMER_H1001 19.04.2016 2 Industry Usage
 O 50001755 ZZCUSTOMER_H1001 19.04.2016 2 Industry Usage
 O 50001757 ZZCUSTOMER_H1001 19.04.2016 2 Industry Usage
 O 50001774 ZZCUSTOMER_H1001 19.04.2016 2 Industry Usage
 O 50002056 ZZCUSTOMER_H1001 19.04.2016 2 Industry Usage

43 /47
 A I M RE A DY RE CK O N E R: SD & CRM

For Application:

 ZCSGL_SORG_AIM4 (Sales Org Pre-requisites)

 O 50000609O 50000519
 O 50000609
 O 50000611
 O 50000829
 O 50000968
 O 50000983
 O 50001060
 O 50001073
 O 50001461
 O 50001616
 O 50001755
 O 50001757
 O 50001774
 O 50002056
 O 50007583
 O 50007584
 O 50007585
 O 50007586
 O 50007587
 O 50000611
 O 50000829
 O 50000968
 O 50000983
 O 50001060
 O 50001073
 O 50001616
 O 50001755
 O 50001757
 O 50001774
 O 50002056
 O 50007583
 O 50007584
 O 50007585
 O 50007586
 O 50007587

 ZCSGL_APPL_AIM (BU Pre-requisites)


DMDR
DMMG
DMPC

44 /47
 A I M RE A DY RE CK O N E R: SD & CRM

DMRO
PGGA
PGGI
PGGS
 DMDR 00.00.0000 31.12.2016
 DMMG 00.00.0000 31.12.2016
 DMPC 00.00.0000 31.12.2016
 DMRO 00.00.0000 31.12.2016
 IAPG 01.01.2017 31.12.9999
 IASC 01.01.2017 31.12.9999
 PAPG 01.04.2016 31.12.2016
 PGGA 00.00.0000 00.00.0000
 PGGI 00.00.0000 00.00.0000
 PGGS 00.00.0000 00.00.0000
 RMDR 01.01.2017 31.12.9999
 RMMG 01.01.2017 31.12.9999
 RMRO 01.01.2017 31.12.9999
 RMSC 01.01.2017 31.12.9999

For Vessel Type & Crane:

 ZCSGL_SORG_AIM4 (Sales Org Pre-requisites)

 O 50000609
 O 50000611
 O 50000829
 O 50000968
 O 50000983
 O 50001060
 O 50001073
 O 50001616
 O 50001755
 O 50001757
 O 50001774
 O 50002056
 O 50007583
 O 50007584
 O 50007585
 O 50007586
 O 50007587
 O 50000519

45 /47
 A I M RE A DY RE CK O N E R: SD & CRM

 O 50001461

 ZCSGL_VSL_AIM (BU Pre-requisites)

 PAMA
 PATU
 IAMP 01.01.2017 31.12.9999
 IASC 01.01.2017 31.12.9999
 IATU 01.01.2017 31.12.9999
 PAMA 00.00.0000 31.12.2016
 PATU 00.00.0000 31.12.2016

For Business Line:

 ZCSGL_SORG_AIM4 (Sales Org Pre-requisites)

 O 50000609
 O 50000611
 O 50000829
 O 50000968
 O 50000983
 O 50001060
 O 50001073
 O 50001616
 O 50001755
 O 50001757
 O 50001774
 O 50002056
 O 50007583
 O 50007584
 O 50007585
 O 50007586
 O 50007587
 O 50000519
 O 50001461

 ZCSGL_VSL_AIM (BU Pre-requisites)

DMDR
DMMG
DMRO
PAOG
PAPG
PGGA
PACT
 DMDR 00.00.0000 31.12.2016
 DMMG 00.00.0000 31.12.2016
 DMRO 00.00.0000 31.12.2016
 IACT 01.01.2017 31.12.9999
 IAOG 01.01.2017 31.12.9999
 IAPG 01.01.2017 31.12.9999
 IAMP 00.00.0000 23.03.2018
 IAPI 00.00.0000 01.07.2017
 PAOG 00.00.0000 31.12.2016
 PAPG 00.00.0000 31.12.2016
 PGGA 00.00.0000 00.00.0000
 PGGI 00.00.0000 00.00.0000
 PGGS 00.00.0000 00.00.0000
 RMDR 01.01.2017 31.12.9999

46 /47
 A I M RE A DY RE CK O N E R: SD & CRM

 RMMG 01.01.2017 31.12.9999

 RMRO 01.01.2017 31.12.9999
 RMSC 01.01.2017 31.12.9999
 PACT 00.00.0000 31.12.2016

For Service Category

 ZCSSRVCAT_ACTDATE (TVARVC Variable - Sales Org wise Activation date)

 O 50000609 03.04.2015
 O 50000611 03.04.2015
 O 50000829 03.04.2015
 O 50000968 03.04.2015
 O 50000983 03.04.2015
 O 50001060 03.04.2015
 O 50001073 03.04.2015
 O 50001181 03.04.2015
 O 50001616 03.04.2015
 O 50001755 03.04.2015
 O 50001757 03.04.2015
 O 50001774 03.04.2015
 O 50007583 03.04.2015
 O 50007584 03.04.2015
 O 50007585 03.04.2015
 O 50007586 03.04.2015
 O 50007587 03.04.2015
 O 50000519 23.03.2016
 O 50001461 23.03.2016

 ZCSSRVCAT_TRTYPE (TVARVC Variable – Pre-requisite Service Order Types)


 ZFSO
 ZCCM
 ZFSI
 ZPRT
 ZSCU
 ZCCR
 ZCMR
 ZQPC

47 /47