Académique Documents
Professionnel Documents
Culture Documents
Compliance
Installation & Customizing
for SAP
ERP
July 22, 2009
Trademarks are not explicitly marked as such in this product information as is the norm in technical
documentation.
All the product names used herein are assumed to be registered trademarks of the respective
company.
All trademarks are recognized.
SAP
System 26
3.10.2 Menu Names in the Monitor in an SAP
R/3
4.7 System 26
3.10.3 Error Message "not_supported_gui" 26
3.10.4 Which SAP
Tables Are Tested with ATC :: Compliance? 27
3.10.5 Which SAP
Transactions Are Affected? 27
4 Customizing 29
4.1 Customizing for the Communication between ATC :: Compliance and Compliance Engine 29
4.1.1 Defining Target Systems for RFC Calls 29
4.1.2 Compliance Engine Settings 29
4.1.3 Compliance Alert Agent Settings 29
4.2 Customizing the Blocks 30
ii ATC :: Compliance Installation and Customizing
4.2.1 Defining Blocking Reasons for Billing/Shipping/FI 30
4.2.2 Assigning Z-Keys 33
4.3 Customizing for ATC :: Compliance Screening 34
4.3.1 Maintaining Roles for ATC :: Compliance Screening 34
4.3.2 Creating Jobs 39
4.4 Customizing for Compliance Screening for SAP
CRM 41
4.5 Customizing for ATC :: Export Controls 41
4.5.1 Maintaining Roles for ATC :: Export Controls 42
4.5.2 What to Do if the Export Data Sheet is not Displayed with the Customer 43
4.5.3 Creating Jobs for Export Controls 46
4.6 Checking Customizing 46
4.7 Changing the Customizing in the Productive System 46
5 Enhancements and Entry Points for Project Developments 48
5.1 Enhancements of the Material for ATC :: Export Controls 48
5.2 Business Add-Ins 51
5.3 Interfaces for Customer Extensions 57
5.3.1 /AEB/CMP_EC_PUBLIC Access to the Export Controls Transaction 57
5.3.2 /AEB/CMP_PUBLIC_BLK_CHK Access to the Block Entries in the Monitor 57
5.3.3 /AEB/CMP_PUBLIC_INFO Access to Settings 58
5.3.4 /AEB/CMP_PUBLIC_SCR_CHECK Access to Checks, Logging and Mail
Functions 59
6 Appendix: Details on the Application Settings for Compliance
Screening 64
6.1 Compliance Screening Settings for SD 65
6.2 Compliance Screening Settings for MM 67
6.3 Compliance Screening Settings for FI 68
ATC :: Compliance Installation and Customizing 1
1 Record of Modifications
Service Pack Modification Chapter
(Cross Reference)
02/2009 Mit ATC :: Compliance geprfte SAP
systems and the Compliance Engine must all be on the same network.
3.2 Which User Rights Are Required for Installation and
Customizing?
3.2.1 Dialog Users
The following authorizations are required in order to integrate and customize the
ATC :: Compliance functions in the development system:
CMOD Table Enhancement
SE80 ABAP Workbench
SM30 Table View Maintenance
SE38 ABAP Editor: Entry level (for starting ATC :: programs)
SE11 ABAP Dictionary
SE19 BadI Builder
SMLT Language Management
SE11 ABAPTM Dictionary
SE16N General Table View
SE24 Class Builder
SE14 Database Utility
SM51 SAP Server
SPRO ATC :: settings under Sales and Distribution > Foreign
Trade/Customs > Legal Control > ATC :: Compliance)
SM59 Display and maintain RFC destinations
SBWP Start Business Workplace
SO01 Business Workspace inbox
OMR9 Payment Block Reasons
ST22 ABAPTM Runtime Error
SM21 SysLog: Local Evaluation
ATC :: Compliance Installation and Customizing 4
SU01 User Maintenance
SMGW Gateway Monitor
SM36 Job Definition
SM37 Job Selection
SE10 Transport Organizer
STMS Transport Management System
+ Development User (i.e. development key)
Transactions from the SD environment for the dialog user:
XD01, XD02, XD03 Create, edit, display customer
MK01, MK02, MK03 Create, edit, display vendor
VA01, VA02, VA03 Create, edit, display order
VL01N, VL02N, VL03N Create, edit, display delivery
SE38 (for starting batch check reports)
AEB-specificworking with the Compliance Engine (after importing AEB transports to
SAP system):
/aeb/cmpconsole Web front end Engine
/aeb/cmpconsistence Consistency check
/aeb/cmpmonitor ATC :: Compliance Monitor
/aeb/cmpadrcheck Address check without login
/aeb/cmpprotentry Manual notice of CE log entry
/aeb/cmpbatches Dialog for the AEB batches
It is also advisable to give the user the role SAP_BC_ENDUSER.
3.2.2 Communications Users (CPIC Users)
A TCP/IP RFC destination is created under which the program ID is stored.
The Compliance Engine must also registered with the SAP
system to call
RFMs via the RFC (authorization object S_RFC, ACTVT: 16 RFC_TYPE: FUGR).
Depending on the SAP
data
dictionary. This service itself calls up several function modules (RFMs) internally in the SAP
system. This requires specific authorizations to access function groups.
Solution: Users who wish to use the repository service must be authorized in the SAP
system to
call RFMs via the RFC (authorization object S_RFC, ACTVT: 16 RFC_TYPE: FUGR).
Depending on the SAP
note 330267.
This action must be repeated for each system to which the transport is imported (development,
consolidation, production).
How are transport profile parameters added/modified?
The transport profile parameters can only be modified from the transport domain controller.
Log on to the transport domain controller.
Launch the STMS transaction.
From the Overview menu, select System Overview (Shift+F6).
Double-click on the system of your choice.
ATC :: Compliance Installation and Customizing 7
Switch to the Transport tool Sheet.
Here the setunicodeflag parameter can be added.
After the TMS configuration is saved, it must be distributed. Please confirm the message that
follows.
3.3.2 Importing the Transport Request
The transport request files including documentation can be found in the AEB customer portal at
www.myaeb.com (regarding login details and instructions for use, please get in touch with your
AEB contact person). Please make sure that you take the correct version.
The ATC_CMP_*.zip file contains the following:
\doc\ Documentation about installation, application and interface.
\trans\ Basis transport
\Servicepaket\trans\ Service pack transport
Copy these files to any client in your SAP
R/3
Settings entry in the Administration Cabinet. Select the desired line(s) and
initiate restart via the RFC server menu.
3.5 Filling In User Exits and Customer Exits
3.5.1 User Exits
Please request object keys from SAP
for the following objects if they have not yet been unlocked.
You should have these object keys ready prior to installation.
Object Object key
R3TR PROG MV45ATZZ
ATC :: Compliance Installation and Customizing 9
Object Object key
R3TR PROG MV45AFZZ
R3TR PROG MV50ATZZ
R3TR PROG MV50AFZ1
Important information
Object keys can be obtained from the SAP
object.
The SAP
code for ATC :: Compliance may only be modified using the Modification Assistant. The
functions Insert, Replace, Delete and Cancel are available here.
To insert an enhancement in the SAP
code, place the cursor at the desired position and click the
Insert button.
Your SAP
system creates an insert at this position. The blue asterisk indicates the position where
an entry is possible:
All that remains now is to fill in the new code and save the include. If possible, activate the code.
(Make sure you activate the includes of the data declarations *ATZZ before the corresponding save
includes *AFZZ!) It may be necessary to create a transport request that will be needed for the
subsequent transport into the productive system.
ATC :: Compliance Installation and Customizing 10
Make the following entries in the individual user exits:
MV45ATZZ
* =====================================================================
* Start: ATC::Compliance Screening
* ---------------------------------------------------------------------
INCLUDE /AEB/CMP_ORD_GLOBAL_DATA.
* ---------------------------------------------------------------------
* Ende: ATC Compliance Screening
* =====================================================================
MV45AFZZ : USEREXIT_SAVE_DOCUMENT
* =====================================================================
* Start: ATC Compliance Screening
* ---------------------------------------------------------------------
INCLUDE /AEB/CMP_ORD_AFTER_SAVE.
* ---------------------------------------------------------------------
* Ende: ATC Compliance Screening
* =====================================================================
MV45AFZZ : USEREXIT_SAVE_DOCUMENT_PREPARE
* =====================================================================
* Start: ATC Compliance Screening
* ---------------------------------------------------------------------
INCLUDE /AEB/CMP_ORD_BEFORE_SAVE.
* ---------------------------------------------------------------------
* Ende: ATC Compliance Screening
* =====================================================================
MV50ATZZ
* =====================================================================
* Start: ATC Compliance Screening
* ---------------------------------------------------------------------
INCLUDE /AEB/CMP_DELV_GLOBAL_DATA.
* ---------------------------------------------------------------------
* Ende: ATC Compliance Screening
* =====================================================================
MV50AFZ1 : USEREXIT_SAVE_DOCUMENT
* =====================================================================
* Start: ATC Compliance Screening
* ---------------------------------------------------------------------
INCLUDE /AEB/CMP_DELV_AFTER_SAVE.
* ---------------------------------------------------------------------
* Ende: ATC Compliance Screening
* =====================================================================
MV50AFZ1 : USEREXIT_SAVE_DOCUMENT_PREPARE
* =====================================================================
* Start: ATC Compliance Screening
* ---------------------------------------------------------------------
INCLUDE /AEB/CMP_DELV_BEFORE_SAVE.
* ---------------------------------------------------------------------
* Ende: ATC Compliance Screening
ATC :: Compliance Installation and Customizing 11
* =====================================================================
3.6 Filling In Customer Exits
How are customer exits filled in?
Create a development class or packet in the SE80 transaction.
It may be necessary to create a transport request that will be needed for the subsequent transport
into the productive system.
Customer exits require an enhancement project. Use the CMOD transaction to create an
enhancement project.
ATC :: Compliance Installation and Customizing 12
Enter the project name, select Enhancement assignment and click Create.
Next, create a short text and click Enhancement assignments.
A development class or a packet is requested first. Enter the development class or packet created
above.
Now enter all the enhancements for the enhancement project:
MM06E005, SAPMF02D and SAPMF02K.
ATC :: Compliance Installation and Customizing 13
Click the Components button to fill the corresponding customer exits.
Double-click the relevant customer exit (function exits: EXIT_SAPMF02D_001,
EXIT_SAPMF02K_001, EXIT_SAPMM06E_013) to jump to the associated function module.
ATC :: Compliance Installation and Customizing 14
Double-click here to select the entered include. If it is not available, a system query appears asking
whether you wish to create the include. Confirming the dialog and assigning the development class
or packet created above brings you to the include.
Here the AEB program code must be entered.
Make the relevant entries for all the includes and activate them.
ATC :: Compliance Installation and Customizing 15
Return to the project overview and activate it to apply the includes.
You can see that the project has been activated when the red alerts have changed into green
lights.
Make the following entries in the includes of the customer exits:
In the include ZXF04U01 (function EXIT_SAPMF02D_001)
* =====================================================================
* Start: ATC Compliance Screening
* ---------------------------------------------------------------------
INCLUDE /AEB/CMP_START_CUST_ONL_CHECK.
* ---------------------------------------------------------------------
* Ende: ATC Compliance Screening
* =====================================================================
In the include ZXF05U01 (function EXIT_SAPMF02K_001)
* =====================================================================
* Start: ATC Compliance Screening
* ---------------------------------------------------------------------
INCLUDE /AEB/CMP_START_VDR_ONL_CHECK.
* ---------------------------------------------------------------------
* Ende: ATC Compliance Screening
* =====================================================================
In the include ZXM06U44 (function EXIT_SAPMM06E_013)
* =====================================================================
* ATC::Compliance checks start
ATC :: Compliance Installation and Customizing 16
* ---------------------------------------------------------------------
INCLUDE /AEB/CMP_START_PD_ONL_CHECK.
* ---------------------------------------------------------------------
* ATC::Compliance checks end
* =====================================================================
Note:
SAP
offers six screen exits in the enhancement MM06E005 for purchasing documents. The
screens for these exits have to be implemented.
How are customer exit screens implemented empty?
Double-click on the corresponding screen exit.
The following system information window appears:
The Screen Painter is then displayed:
ATC :: Compliance Installation and Customizing 17
Do the following:
Enter a brief description.
Select Subscreen as the screen type.
It is now possible to customize the layout.
Click Save to continue.
You are then prompted for the development class or packet:
The screen can then be activated ( ).
ATC :: Compliance Installation and Customizing 18
The screen exit is now implemented.
All six screens of the exit must be implemented in this manner, as interruptions in SAP
may
otherwise result.
3.7 Filling In Business Add-Ins
Depending on the version of your SAP
database.
Start the SE11 transaction and click Display to see the desired SAP
performance trace.
ATC :: Compliance Installation and Customizing 26
Follow the same procedure to create a database index for the VBAK table.
3.10 Tips and Tricks
3.10.1 Important Information for the Use of Unicode in an SAP
System
Under Administration, go to the SAP
system and the Compliance Engine, this Unicode marker is maintained in the
WSM, not in the Compliance Engine.
If the SAP
system uses Unicode, specify that the target system is a Unicode system in the RFC
connection parameters as well.
3.10.2 Menu Names in the Monitor in an SAP
R/3
4.7 System
If the menu names in the Monitor of an SAP
R/3
system do not work here for reasons that are not clear.
Correct this problem in one of the following manners:
Transaction SE80, display and double-click the "/AEB/CMP11_MONITOR" program and select
the menu item Program > Generate.
When the generation is complete, be sure to enter the command "/$CUA" on each application
server to reset the CUA buffer (see SAP
system. Registration is carried out using a TCP/IP connection (type T) and a Program ID which
must be identical to the Engines Program ID.
Under Connection type, select Registration; for the Program ID, use ATCC, for example.
Next, test the connection by clicking on the Test connection button. This will work only when the
Compliance Engine has been properly configured and registered correctly with the SAP
R/3
system.
Important information for Unicode in a 4.7 system
In the RFC connection parameters of an SAP
system.
4.1.2 Compliance Engine Settings
In Customizing (SPRO transaction), open the branch Sales > Foreign Trade/Customs > Legal
Control > ATC :: Compliance > Application settings > Compliance Engine settings.
Begin by entering the name of the RFC destination for the Compliance Engine that was created
earlier in the Destination field.
Continue by selecting an Engine client and Engine profile. These entries originate from the
Compliance Engine. If it is not possible to make a selection here, the Engine is not fully connected
to the SAP system!
The Engine profile defines the settings for the compliance screening. This includes, for example,
the threshold value for similarity checks or the restricted party lists used for the screening.
4.1.3 Compliance Alert Agent Settings
The Alert Agent offers the possibility of an automatic emergency deactivation for ATC ::
Compliance in case the connection to the Compliance Engine is disrupted for a longer period of
time. If such an emergency deactivation occurs, all checks of ATC :: Compliance will be
deactivated. This will be recorded in log entries and your administrators will be notified via SAP
office mail.
The configuration of the Alert Agent is not mandatory. It should only be made if you really need this
automatic emergency deactivation.
ATC :: Compliance Installation and Customizing 30
The Alert Agent analyzes the calls made to the Compliance Engine for 15 minutes. If the defined
percentage of error calls is exceeded, ATC :: Compliance will be deactivated.
If an emergency deactivation occurred, ATC :: Compliance can only be reactivated manually
by using transaction /AEB/CMPEMERGENCY. See also chapter 4.7 on page 46).
To make the Alert Agent work, two steps are required:
Setting up the Alert Agent
Set up the report /AEB/CMP_ALERT_AGENT as a batch job in the client screened by ATC ::
Compliance. The job is to be scheduled with a period of one minute.
Defining settings for the Alert Agent
In Customizing (SPRO transaction), open the branch Sales > Foreign Trade/Customs > Legal
Control > ATC :: Compliance > Applications Settings and open Compliance Alert Agent
settings there.
Activate the Agent using the Activate option in the main settings.
Define the minimum amount of calls required within the analysing period of 15 minutes in
order to enable the analysis. If the Compliance Engine is called less often within this period,
the analysis for this period will be canceled.
Define the percentage of error calls in order to provoke an emergency deactivation.
For example, if you enter 50% here and the Agent would check 100 calls, the system would
switch to emergency mode after 50 error calls.
The transaction /AEB/CONSISTENCY tells you whether the configuration is complete.
4.2 Customizing the Blocks
4.2.1 Defining Blocking Reasons for Billing/Shipping/FI
In Customizing (SPRO transaction), open the branch Sales > Foreign Trade/Customs > Legal
Control > ATC :: Compliance > Technical Settings > Define Blocking Reasons for Billing/Define
Reasons for Blocking in Shipping/Define Payment Blocking (FI Documents).
Here, free values can be used in your SAP
system.
The same applies to delivery blocks and payment blocks.
Further information
For further information please refer to the documentation of your SAP
system.
ATC :: Compliance Installation and Customizing 34
4.3 Customizing for ATC :: Compliance Screening
In Customizing (SPRO transaction), open the branch Sales > Foreign Trade/Customs > Legal
Control > ATC :: Compliance > Application settings
> Compliance Screening settings for SD
> Compliance Screening settings for MM
> Compliance Screening settings for FI
Here, you define the parameters for the ATC :: Compliance Screening module within the framework
of your SAP
system.
4.3.1 Maintaining Roles for ATC :: Compliance Screening
In the SAP
user administration (SAP menu > Tools > Administration > User Maintenance > SU01
- Users), users can be assigned one or more roles, which may include the authorization object
ZAEB_CMPAD. This role must first be created, however.
How are roles created and maintained?
Any user who requires additional authorizations to use ATC :: Compliance must have the following
authorization objects available in his or her profile.
It is best to create a separate role for this.
The PFCG transaction brings you to role maintenance. Enter a role name here. Then click Create.
ZAEB_CMPAD for use of the Compliance Monitor
ZAEB_CMPTA for the batches and their overview
ZAEB_CMPEC for the rights for export control (see also section 4.5.1 on page 42)
AB SP 08/2007 ZAEB_CMPEM for use of the emergency program (see also section 4.7 on
page 46)
ATC :: Compliance Installation and Customizing 35
To create an authorization profile, switch to the Authorizations tab. You will be prompted to save
the role. Click Yes to confirm.
ATC :: Compliance Installation and Customizing 36
Click Change authorization data to create a new profile.
Do not select templates.
ATC :: Compliance Installation and Customizing 37
Now click Manually and enter the authorization object (e.g. ZAEB_CMPAD for the
ATC :: Compliance Administrator).
This adds one more authorization to the role. Click on the pen icon to set this.
When all rights have been defined correctly, the role status is automatically set to green.
Click Manually to enter the authorization object ZAEB_CMPTA as well and define the rights.
The following transaction codes must be entered in the authorization profile.
For this, click again on the Manually button and enter the authorization object S_TCODE.
ATC :: Compliance Installation and Customizing 38
Enter the following transaction in the authorization object.
/aeb/cmpconsole Web front end Engine
/aeb/cmpconsistence Consistency check
/aeb/cmpmonitor ATC :: Compliance Monitor
/aeb/cmpadrcheck Address check without login
/aeb/cmpprotentry Manual notice of CE log entry
/aeb/cmpbatches Dialog for the AEB batches
ATC :: Compliance Installation and Customizing 39
The role must then still be generated ( ).
On the User tab, enter all the users to whom you wish to assign this role. When you are finished,
click the User compare button and select Full comparison.
Further information
For further information please refer to the User Manual and the documentation of your SAP
system.
4.3.2 Creating Jobs
You can create different jobs to check the various address types and documents in your SAP
system and to delete old log entries. The results of the individual job runs are displayed in
ATC :: Compliance Monitor.
Proceed as follows to configure the jobs:
1. Open the ATC :: Compliance Batches application using the transaction /N/AEB/
CMPBATCHES.
2. Click the icon to the right of the desired job.
ATC :: Compliance Installation and Customizing 40
3. You can use the fields in the Filter field group to scale the job and limit the check to various
subsets of the address data.
If you leave the filter parameters blank, the check includes all relevant address data (all
customers, for example) of the current client.
4. In the ATC :: Compliance Engine parameters field group, you can define settings for
Destination, Engine client and Engine profile that differ from the parameters in the Compliance
Engine settings (SPRO SAP reference IMG).
This allows you to select from different profiles. For example, you can use a different threshold
for the nightly batch check than you use for the online check. (Online checks are launched
when an address defined under the Compliance Engine settings is edited, for example.)
5. The Job settings or Job parameters field group is available for only some of the jobs described
here. Here you can define settings that apply to blocks.
Details on various job types can be found in the next section.
You can also use transaction SE38. Here you can use the program names listed under
Program names and transactions of individual job types on page 41.
Details on specific job types
Check customer master data: In the Compliance Screening settings for SD (SPRO SAP
reference IMG), you can define the default values for blocks to be set. These default values can be
overwritten in individual jobs.
The Job settings field group offers the Update each KNEX date option. Enabling this option means
that the Boycott date field on the Export data Sheet is updated when the customer is screened.
This date is set whenever a customer is first blocked. It is updated in subsequent batch runs only if
this option is enabled.
Check sales documents: If the Compliance inactive filter criterion in the Filter field group is
selected, the batch examines all the documents that have the Compliance inactive block as the
delivery or billing block.
The Job settings field group on the General sheet lets you define whether you wish to run a
simulation in which no blocks are set or lifted. Select the appropriate option and configure the other
job settings as you normally would. The simulation also generates messages and log entries.
If you have also installed the Export Controls module, the Job parameters field group offers the
following additional options:
The General sheet lets you define whether you wish to run a simulation in which messages
and log entries are generated but no blocks are set or lifted.
The Export Controls sheet lets you define whether blocks should be set or overwritten if export
restrictions are detected.
Check vendor master data: In the Compliance Screening settings for SD (SPRO SAP reference
IMG), you can define the default values for blocks to be set. These default values can be
overwritten in individual jobs.
Check employee master data: In the Compliance Screening settings for SD (SPRO SAP
reference IMG), you can define whether the job may be run.
Check applicant master data: In the Compliance Screening settings for SD (SPRO SAP
reference IMG), you can define whether the job may be run.
Check bank master data: In the Compliance Screening settings for FI (SPRO SAP reference
IMG), you can define a default value for whether banks should be flagged as suspicious and added
to ATC :: Compliance Monitor. This default value can be overwritten in individual jobs.
ATC :: Compliance Installation and Customizing 41
Check financial documents: In the Compliance Screening settings for FI (SPRO SAP reference
IMG), you can define a default value for whether blocks should be set. This default value can be
overwritten in individual jobs.
Program names and transactions of individual job types
Job type Name of program Transaction
Check customer master
data
/AEB/CMP_DEBITOR_CHECK_FOR_JOB /AEB/CMP_DEB_CHECK
Check sales documents /AEB/ CMP_SALES_DC_CHK_FOR_JOB /AEB/CMP_SALES_CHECK
Check vendor master data /AEB/CMP_VENDOR_CHECK_FOR_JOB /AEB/CMP_VDR_CHECK
Check employee master
data
/AEB/CMP_EMPL_CHECK_FOR_JOB /AEB/CMP_EMPL_CHECK
Check applicant master data /AEB/CMP_APPL_CHECK_FOR_JOB /AEB/CMP_APPL_CHECK
Check bank master data /AEB/CMP_BANK_CHCK_FOR_JOB /AEB/CMP_BANK_CHECK
Check financial documents /AEB/ CMP_FI_ACC_DC_CHK_FOR_JOB /AEB/CMP_FI_DC_CHECK
Delete log entries /AEB/CMP_DELETE_LOG_FOR_JOB
4.4 Customizing for Compliance Screening for SAP
CRM
If you use the Compliance Screening for SAP
system.
4.5.1 Maintaining Roles for ATC :: Export Controls
In the SAP
user administration (SAP menu > Tools > Administration > User Maintenance > SU01
- Users), users can be assigned one or more roles, which may include the authorization object
ZAEB_CMPEC.
Maintain the role as described in Chapter 3.3.1, Maintaining Roles for ATC :: Compliance
Screening. Follow the same procedure to create a role or enhance an existing Compliance role.
The authorization object ZAEB_CMPEC for Export Controls must be added to the role.
Authorizations can be granted for the following types of test results:
Todo
License required
ATC :: Compliance Installation and Customizing 43
Restriction
Error
Once the authorization has been granted, the user can release the Export Controls test results of
the corresponding type.
Further information
For further information please refer to the User Manual and the documentation of your SAP
system.
4.5.2 What to Do if the Export Data Sheet is not Displayed with the
Customer
This sheet only appears depending on the account group!
/xd02
The account group can be found with the Customer under Details >> Administration data
(Shift + F8)
(A Treasury Customer has the account group DEBI, for example).
Now you can check in the SAP
revision
history.
ATC :: Compliance Installation and Customizing 48
5 Enhancements and Entry Points for Project
Developments
5.1 Enhancements of the Material for ATC :: Export Controls
ATC :: Export Controls requires enhancement of the export session of the material by one
subscreen.
The various layers can be configured to one material in the SAP
material
master screen sequence defines the sequence of information elements.
ATC :: Compliance Transport already includes its own function group, /AEB/CMP_EC_MARC_GUI.
This function group contains the prepared screen 2000, which can be integrated into the export
session.
How are material master screen sequences maintained in the SAP
system?
The views of a material can vary by user, industry sector, material type, plant and entry/display
transaction.
Adding a field group to a view is one step. Another step is to assign when a view is used for whom
and in which cases.
Define Structure of Data Screens for Each Screen Sequence
Here it is the enhanced screen sequence 21 (industry standard short screens).
ATC :: Compliance Installation and Customizing 49
Highlight screen sequence 21 and double-click on Data screens.
Next, highlight the entry 21 / 12 Foreign Trade: Export Data and double-click on Subscreens.
ATC :: Compliance Installation and Customizing 50
All subscreens numbered 0001 are empty subscreens and can be replaced.
ATC :: Compliance Installation and Customizing 51
This requires entering the program name /AEB/SAPLCMP_EC_MARC_GUI and the screen no.
2000.
Now save the setting.
Maintaining user settings
You still must maintain the user settings for the new screen sequence.
Example:
5.2 Business Add-Ins
The following overview shows the business add-ins for ATC :: Compliance. For further information,
refer to the online documentation for the business add-ins (SE19 transaction).
Name Area Function(s)
/AEB/CMP_ACC_DC_03 Financial
document batch
check
Trigger additional mails/actions if:
a partner was classified as suspicious.
an error occurred during the check.
a partner was not classified as suspicious.
/AEB/CMP_APPLICAN_03 Applicant batch
check
Trigger additional mails/actions if:
the applicant was classified as suspicious.
an error occurred during the check.
the applicant was not classified as suspicious.
/AEB/CMP_BANK_03 Bank batch check Trigger additional mails/actions if:
the bank was classified as suspicious.
an error occurred during the check.
the bank was not classified as suspicious.
ATC :: Compliance Installation and Customizing 52
Name Area Function(s)
/AEB/CMP_CUSTOMER_01 Customer online
check
Determine whether individual customers should
be checked.
Define different Engine parameters (destination,
Engine client, Engine profile) for the check of this
customer.
/AEB/CMP_CUSTOMER_02 Customer online
check
Trigger additional mails/actions if:
the customer was classified as suspicious.
an error occurred during the check.
the customer was not classified as suspicious.
/AEB/CMP_CUSTOMER Customer batch
check
Trigger additional mails/actions if:
the customer was classified as suspicious.
an error occurred during the check.
the customer was not classified as suspicious.
a previously suspicious customer was reclassified
as unsuspicious.
/AEB/CMP_DLV_DC_01 Delivery online
check
Determine whether individual deliveries should be
checked.
Define different Engine parameters (destination,
Engine client, Engine profile) for the check of this
delivery.
/AEB/CMP_DLV_DC_02 Delivery online
check
Trigger additional mails/actions if:
the delivery includes suspicious addresses.
an error occurred during the check.
the delivery does not include any suspicious
addresses.
/AEB/CMP_DLV_DC_03 Delivery online
check
Exclude partner from the screening.
/AEB/CMP_EC_ORDER_01 Sales documents
Export Controls
Determine whether individual sales documents are
subject to the Export Controls check.
/AEB/CMP_EC_ORDER_02 Export Controls Modify the generated Export Controls data to be
checked by the Compliance Engine.
/AEB/CMP_EMPLOYEE_03 Personnel master
batch check
Trigger additional mails/actions if:
the personnel master record was classified as
suspicious.
an error occurred during the check.
the personnel master record was not classified as
suspicious.
/AEB/CMP_MAT_DC_01 Goods receipt
online check
Determine whether individual goods receipts
should be checked.
Define different Engine parameters (destination,
Engine client, Engine profile) for the document
check.
/AEB/CMP_MAT_DC_02 Goods receipt
online check
Trigger additional mails/actions if:
the document includes suspicious addresses.
an error occurred during the check.
the document does not include any suspicious
addresses.
/AEB/CMP_MONITOR_01 Monitor/deliveries Trigger additional mails/actions if:
delivery is unblocked.
/AEB/CMP_MONITOR_02 Monitor Define different Engine parameters (destination,
Engine client, Engine profile) for the Good Guy
definitions, unblocking and restricted parties.
ATC :: Compliance Installation and Customizing 53
Name Area Function(s)
/AEB/CMP_MONITOR_03 Monitor Additional filter options for the Monitor to determine
whether entries should be shown. Implemented for:
Customers
Vendors
Sales documents
Deliveries
Purchasing documents
Material documents
Banks
Financial documents
Personnel master
Applicants master
/AEB/CMP_PURCH_DC_01 Purchasing
document online
check
Determine whether individual documents should
be checked.
Define different Engine parameters (destination,
Engine client, Engine profile) for the document
check.
/AEB/CMP_PURCH_DC_02 Purchasing
document online
check
Trigger additional mails/actions if:
the document includes suspicious addresses.
an error occurred during the check.
the document does not include any suspicious
addresses.
/AEB/CMP_SALES_DC_01 Sales document
online check
Determine whether individual documents should
be checked.
Define different Engine parameters (destination,
Engine client, Engine profile) for the document
check.
/AEB/CMP_SALES_DC_02 Sales document
online check
Trigger additional mails/actions if:
the document includes suspicious addresses.
an error occurred during the check.
the document does not include any suspicious
addresses.
/AEB/CMP_SALES_DC_03 Sales document
batch check
Trigger additional mails/actions if:
a partner was classified as suspicious.
an error occurred during the check.
a partner was not classified as suspicious.
/AEB/CMP_SALES_DC_04 Sales document
online and batch
check
Exclude partner from the screening.
/AEB/CMP_VENDOR_01 Vendor online
check
Determine whether individual vendors should be
checked.
Define different Engine parameters (destination,
Engine client, Engine profile) for the check of this
vendor.
/AEB/CMP_VENDOR_02 Vendor online
check
Trigger additional mails/actions if:
the vendor was classified as suspicious.
an error occurred during the check.
the vendor was not classified as suspicious.
ATC :: Compliance Installation and Customizing 54
/AEB/CMP_VENDOR_03 Vendor batch
check
Trigger additional mails/actions if:
the vendor was classified as suspicious.
an error occurred during the check.
the vendor was not classified as suspicious.
a previously suspicious vendor was reclassified
as unsuspicious.
How are ATC :: Compliance business add-ins customized?
Example: You wish to except certain goods receipt documents from checks.
Launch the SE19 transaction.
Select any implementation name (usually in the Z range).
Select the appropriate AEB business add-in name as the definition name (e.g.
/AEB/CMP_MAT_DC_01).
ATC :: Compliance Installation and Customizing 55
Maintain the short text.
Double-click the method you wish to edit.
Clicking on Example implementation class and Definition document provides other useful
information.
Implement the coding. Example:
ATC :: Compliance Installation and Customizing 56
METHOD /aeb/if_ex_cmp_mat_dc_01~is_object_to_check.
* Do not subject goods receipt for order to Compliance check
IF im_mkpf_to_check-vgart ='WF'.
ch_is_object_to_check = space.
ENDIF.
ENDMETHOD.
Click Signature to display the inbound and outbound parameters.
Save. Attention! During the initial creation, activation generates errors. In this case, just save
and return to the main overview, from where you can activate the entire implementation.
This implements the business add-in. It will run before the compliance check is called.
ATC :: Compliance Installation and Customizing 57
5.3 Interfaces for Customer Extensions
For the interface, there is a functional group available containing defined functional modules which
ensure controlled access to the data of ATC :: Compliance.
These functions are divided into four groups:
Functions allowing access to export controls transactions (/AEB/CMP_EC_PUBLIC)
Functions allowing access to blocked entries in the ATC :: Compliance Monitor
(/AEB/CMP_PUBLIC_BLK_CHK)
Functions allowing access to settings (/AEB_CMP_PUBLIC_INFO)
Functions allowing access to checks, logging and mail functions
(/AEB_CMP_PUBLIC_SCR_CHECK)
The individual functions are described in the following:
5.3.1 /AEB/CMP_EC_PUBLIC Access to the Export Controls Transaction
Function module: FUNCTION /aeb/cmp_delete_ec_for_vbeln
With this function, all relevant export controls data relating to a specific sales document will be
deleted. The function expects a key of the sales document as import parameter (VBELN_VA).
Import parameter:
IM_VBELN TYPE VBELN_VA
5.3.2 /AEB/CMP_PUBLIC_BLK_CHK Access to the Block Entries in the
Monitor
Function module: FUNCTION /aeb/cmp_chk_if_md_is_blocked
With this function, it is checked whether a material document has already been blocked. The
function expects the number of the material document as import parameter (MBLNR). A boolean is
returned. X means that the document is blocked.
Import parameter:
IM_MKPF_MBLNR TYPE MBLNR
Export parameter:
RE_IS_BLOCKED TYPE /AEB/BS_E_BOOLEAN
Function module: FUNCTION /aeb/cmp_chk_if_pd_is_blocked
With this function, it is checked whether a purchasing document has already been blocked. The
function expects the number of the purchasing document as import parameter (EBELN). A boolean
is returned. X means that the document is blocked.
Import parameter:
IM_EKKO_EBELN TYPE EBELN
Export parameter:
RE_IS_BLOCKED TYPE /AEB/BS_E_BOOLEAN
ATC :: Compliance Installation and Customizing 58
Function module: FUNCTION /aeb/cmp_chk_if_sd_is_blocked
With this function, it is checked whether a sales document has already been blocked. The function
expects the number of the document as import parameter (VBAK_VBELN). A boolean is returned.
X means that the document is blocked.
Import parameter:
IM_VBAK_VBELN TYPE VBAK-VBELN
Export parameter:
RE_IS_BLOCKED TYPE /AEB/BS_E_BOOLEAN
5.3.3 /AEB/CMP_PUBLIC_INFO Access to Settings
Function module: FUNCTION /aeb/cmp_pb_sd_faksk_comp
With this function, you can read out the block identifier for the billing block in case of Compliance
active.
Export parameter:
EX_FAKSK TYPE FAKSK
Function module: FUNCTION /aeb/cmp_pb_sd_faksk_comp_inac
With this function, you can read out the block identifier for the billing block in case of Compliance
inactive.
Export parameter:
EX_FAKSK TYPE FAKSK
Function module: FUNCTION /aeb/cmp_pb_sd_lifsk_comp
With this function, you can read out the block identifier for the delivery block in case of Compliance
active.
Export parameter:
EX_LIFSK TYPE LIFSK
Function module: FUNCTION /aeb/cmp_pb_sd_lifsk_comp_inac
With this function, you can read out the block identifier for the delivery block in case of Compliance
inactive.
Export parameter:
EX_LIFSK TYPE LIFSK
ATC :: Compliance Installation and Customizing 59
5.3.4 /AEB/CMP_PUBLIC_SCR_CHECK Access to Checks, Logging and
Mail Functions
Function module: FUNCTION /aeb/cmp_addr_chk_for_addr1val
With this function, you can perform a compliance check of an address by using the complete
address as import parameter.
Import parameter:
IM_ADDR1_VAL TYPE ADDR1_VAL
IM_SUPPRESS_ENGINE_LOGGING TYPE CHAR1
IM_RFC_DESTINATION TYPE RFCDEST
IM_ENGINE_CLIENT TYPE /AEB/CMP_ENGN_CLIENT
IM_ENGINE_PROFILE TYPE /AEB/CMP_ENGN_PROFILE
IM_REF_COMMENT TYPE CHAR255
Export parameter:
RE_IS_SUSPICIOUS TYPE CHAR1
Exceptions:
ENGINE_NOT_REACHED
ENGINE_REMOTE_ERROR
UNSPECIFIED_ENGINE_ERROR
Function module: FUNCTION /aeb/cmp_addr_chk_for_addnr
With this function, you can perform a compliance check of an address by using the address
number as import parameter.
Import parameter:
IM_ADDRNR TYPE ADDR1_VAL-ADDRNUMBER
IM_SUPPRESS_ENGINE_LOGGING TYPE CHAR1
IM_RFC_DESTINATION TYPE RFCDEST
IM_ENGINE_CLIENT TYPE /AEB/CMP_ENGN_CLIENT
IM_ENGINE_PROFILE TYPE /AEB/CMP_ENGN_PROFILE
IM_REF_COMMENT TYPE CHAR255
Export parameter:
RE_IS_SUSPICIOUS TYPE CHAR1
Exceptions:
ENGINE_NOT_REACHED
ENGINE_REMOTE_ERROR
UNSPECIFIED_ENGINE_ERROR
ADDRESS_INDETERMINABLE
ATC :: Compliance Installation and Customizing 60
Function module: FUNCTION /aeb/cmp_addr_chk_for_handle
With this function, you can perform a compliance check of an address by using
IM_ADDRHANDLE as import parameter.
Import parameter:
IM_ADDRHANDLE TYPE ADDR1_VAL-ADDRHANDLE
IM_SUPPRESS_ENGINE_LOGGING TYPE CHAR1
IM_RFC_DESTINATION TYPE RFCDEST
IM_ENGINE_CLIENT TYPE /AEB/CMP_ENGN_CLIENT
IM_ENGINE_PROFILE TYPE /AEB/CMP_ENGN_PROFILE
IM_REF_COMMENT TYPE CHAR255
Export parameter:
RE_IS_SUSPICIOUS TYPE CHAR1
Exceptions:
ENGINE_NOT_REACHED
ENGINE_REMOTE_ERROR
UNSPECIFIED_ENGINE_ERROR
ADDRESS_INDETERMINABLE
Function module: FUNCTION /aeb/cmp_customer_scr_check
With this function, you can perform a compliance check of a customer.
Import parameter:
IM_KNB1 TYPE KNB1
IM_KNA1 TYPE KNA1
IM_KNVV TYPE KNVV
IM_SUPPRESS_ENGINE_LOGGING TYPE CHAR1
Export parameter:
RE_IS_SUSPICIOUS TYPE CHAR1
Exceptions:
ENGINE_NOT_REACHED
ENGINE_REMOTE_ERROR
UNSPECIFIED_ENGINE_ERROR
ATC :: Compliance Installation and Customizing 61
Function module: FUNCTION /aeb/cmp_vendor_scr_check
With this function, you can perform a compliance check of a vendor.
Import parameter:
IM_LFA1 TYPE LFA1
IM_LFB1 TYPE LFB1
IM_LFM1 TYPE LFM1
IM_SUPPRESS_ENGINE_LOGGING TYPE CHAR1
Export parameter:
RE_IS_SUSPICIOUS TYPE CHAR1
Exceptions:
ENGINE_NOT_REACHED
ENGINE_REMOTE_ERROR
UNSPECIFIED_ENGINE_ERROR
Function module: FUNCTION /aeb/cmp_md_scr_check
With this function, you can perform a compliance check of a material document.
Import parameter:
IM_MKPF_TO_CHECK TYPE MKPF
IM_SUPPRESS_ENGINE_LOGGING TYPE CHAR1
Export parameter:
RE_IS_SUSPICIOUS TYPE CHAR1
Exceptions:
ENGINE_NOT_REACHED
ENGINE_REMOTE_ERROR
UNSPECIFIED_ENGINE_ERROR
Funktionsbaustein: FUNCTION /aeb/cmp_pd_scr_check
With this function, you can perform a compliance check of a purchasing document.
Import parameter:
IM_EKKO_TO_CHECK TYPE EKKO
IM_SUPPRESS_ENGINE_LOGGING TYPE CHAR1
Export parameter:
RE_IS_SUSPICIOUS TYPE CHAR1
Exceptions:
ENGINE_NOT_REACHED
ENGINE_REMOTE_ERROR
UNSPECIFIED_ENGINE_ERROR
ATC :: Compliance Installation and Customizing 62
Function module: FUNCTION /aeb/cmp_send_mail
With this function, you can send the SAP
mail in any
case.
Sales documents online check field group
Here, you can activate or deactivate the screening for all SD documents without impairing the
entire screening (see above).
With the help of the other settings, you can define orders and/or deliveries are also to be
blocked if the Compliance Engine cannot be reached via the SAP