SAP Interface [PDF]

This section explains how the AutoTime import and export forms and services can be used to import and export data with S

1 downloads 26 Views 528KB Size

Recommend Stories


SAP 101 SAP Overview [PDF]
Dec 20, 2000 - Internet-Business Framework. (through SAP Products and Services). Value Creation. Integrated end-to-end business process. COLLABORATIVE ...... Workflow. The SAP Business Workflow is a support tool that can be used to optimize the execu

SAP Engineering Control Center Interface to SOLIDWORKS
It always seems impossible until it is done. Nelson Mandela

READ PDF SAP Plant Maintenance (SAP PM)
What we think, what we become. Buddha

SAP TCodes - The Best Online SAP Transaction ... - SAP-TCodes.org [PDF]
Sep 30, 2016 - This book is based on our knowledge of SAP system, and it is constantly reviewed to avoid errors; well we cannot warrant full correctness of all content. Use the information and content on this book at your own risk. Published by: book

[PDF] SAP Financial Accounting (SAP FI)
Be like the sun for grace and mercy. Be like the night to cover others' faults. Be like running water

[PDF] SAP FI (SAP Financial Accounting)
Happiness doesn't result from what we get, but from what we give. Ben Carson

SAP Perkuliahan.pdf [PDF]
Mata Kuliah : Konsep Teknologi Informasi C. Fakultas. : Teknologi Industri. Jurusan. : Teknik Informatika. POKOK BAHASAN. MATERI. TUJUAN INSTRUKSIONAL. UMUM. TUJUAN INSTRUKSIONAL. KHUSUS. Min ggu. Referensi. ( lihat ket. pada lembar akhir). 1. Gambar

PdF SAP HANA Certification Guide
In the end only three things matter: how much you loved, how gently you lived, and how gracefully you

SAP
If you are irritated by every rub, how will your mirror be polished? Rumi

Read PDF SAP BW 7.4 (SAP Business Warehouse)
You often feel tired, not because you've done too much, but because you've done too little of what sparks

Idea Transcript


Show Home | AutoTime 7 Help | Features | SAP Interface Support/Contact Us

SAP Interface This section explains how the AutoTime import and export forms and services can be used to import and export data with SAP using IDOCs. The B-COMM for ERP application must also be used to exchange data between AutoTime and SAP. The B-COMM ERP application receives IDOCs from SAP and processes them into XML files that can be read by AutoTime. B-COMM ERP places these XML files in a subfolder where B-COMM ERP is installed (for example, C:\Program Files (x86)\Kaba\B-COMM ERP\AMSProc\Work\IN\Destination). The IN_FILE_WRITER service processes the B-COMM ERP files and places them in the interface_in_queue table. You will need to create a link from the B-COMM ERP folder to the Kaba \import folder. The IN_SAP service converts the IDOC data that is in the in the Interface In Queue form (interface_in_queue table) into a format that AutoTime can read. It then places this data in the in the In XML Queue form (interface_in_xml_queue table). Finally, the IN_SAP service imports the appropriate data from the interface_in_xml_queue tables and into the Charge Element form (charge_element table). The IN_SAP service uses its SENDER_NAME and TRANSACTION_GROUP parameters to look up a record in the Distribution Model that will indicate the Import Name to use. The Import Name, defined in the Import Definition form, defines the source data that will be imported. To export data from AutoTime to SAP, the OUT_SAP service will search for transactions that are eligible to be sent to SAP. The service puts this data in the Out XML Queue form (interface_out_xml_queue table). It then converts the Out XML Queue (interface_out_xml_queue table) data into an IDOC format, and places the data in the Interface Out Queue form (interface_out_queue table). The OUT_SAP service uses its SENDER_NAME and TRANSACTION_GROUP parameters to look up a record in the Distribution Model that will indicate the Export Name to use. The Export Name, defined in the Export Definition form, defines the source data that will be exported. Once the data is in the interface_out_queue table, it can be converted by the OUT_FILE_WRITER service to an XML file to be read by B-COMM ERP. You will need to create a link from the B-COMM ERP folder to the Kaba \export folder so that the OUT_FILE_WRITER service can process the files. On this page: SAP and B-COMM ERP Configuration AutoTime Configuration Requirements for HRMD_A Download Configure the Import Definitions for SAP Configure the Export Rules for SAP HR Exports Configure the Export Definitions for SAP Configure the Interface Host Configure the Process Policy Configure the Distribution Model Configure the Service Instances Supported IDOCs

SAP and B-COMM ERP Configuration 1. Setup the ALE within SAP to be able to communicate to B-COMM ERP and send the IDOCs needed for AutoTime. Once this setup is complete, use the SM59 session within SAP to test for connectivity with B-COMM ERP. 2. Create a database for B-COMM ERP. The following two application settings must be configured in the B-COMM ERP database: enableautoidocexport - Set it to 1 enableautoidocimport - Set it to 1 3. Install the B-COMM ERP application and schema. Make sure there are no port conflicts between AutoTime and B-COMM J2EE. B-COMM ERP must be configured to send IDOCs to SAP. 4. The following services should be running for B-COMM ERP: B-COMM ERP JBOSS B-COMM ERP AMSProc

AutoTime Configuration Requirements for HRMD_A Download Before importing HR data from SAP (SAP_HRMD_A Import Definition), the following items must be configured in AutoTime: Shift Schedule Cycle Hierarchy Definition Hierarchy Elements Facility (Person Group form) Each Facility must also include the HR Hierarchy Level and HR Hierarchy Name settings (in the Person Group Setting tab). These values are used to determine a person’s HOME_LOCATION_HR in their person assignment. Event Filtration Group (Person Group form) Policy Group (Person Group form)

Configure the Import Definitions for SAP The Import Definition form (Main Menu > Configuration > Interfaces > Import Definition) is used to define the SAP source data that you are importing to AutoTime. AutoTime comes with several pre-defined Import Definitions for SAP. It is recommended that you copy the system-defined Import Definitions and use the duplicate versions, which can be modified as necessary. SAP_HRCC1DNCOSTC – Use this Import Definition to import Cost Centers from SAP HR. SAP_HRCC1DNINORD – Use this Import Definition to import Internal Orders from SAP HR. SAP_HRCC1DNWBSEL – Use this Import Definition to import WBS (Work Breakdown Structure) Elements from SAP HR. SAP_HRMD_A – Use this Import Definition to import the following personnel information from SAP HR: Person Data Person Assignments (shift, schedule, pay rate, etc.) Person Groups (facility, policy group, event filtration group) Hierarchies (home location) Note that you must have shifts, schedule cycles, and other settings configured in AutoTime prior to running this download; see above for more information. SAP_OPERA2 – Use this Import Definition to import production planning order operations from SAP. SAP_OPERA3 – Use this Import Definition to import plant maintenance order operations from SAP. SAP_OPERA4 – Use this Import Definition to import project systems order operations from SAP. SAP_WORKC2 - Use this Import Definition to import production planning work centers from SAP. SAP_WORKC3 - Use this Import Definition to import plant maintenance work centers from SAP. SAP_WORKC4 - Use this Import Definition to import project systems work centers from SAP. Using FreeMarker Expressions in the Import Definition The SAP Import Definitions may use FreeMarker expressions to map the SAP data to the correct AutoTime field. For example, the SAP_HRMD_A import uses FreeMarker expressions to set an employee’s Event Filtration Group based on their WERKS (personnel area) and PERSG (employee group) values in SAP.

How the Import Definition is used in the SAP Interface The B-COMM ERP application receives IDOCs from SAP and processes them into XML files that can be read by AutoTime. The IN_FILE_WRITER service processes the B-COMM ERP files and places them in the interface_in_queue table. The IN_SAP service converts the IDOC data that is in the in the Interface In Queue form (interface_in_queue table) into a format that AutoTime can read. It then places this data in the in the In XML Queue form (interface_in_xml_queue table). Finally, the IN_SAP service imports the appropriate data from the interface_in_xml_queue tables and into the Charge Element form (charge_element table). In order to import the appropriate data, the IN_SAP service uses its SENDER_NAME and TRANSACTION_GROUP parameters to look up a record in the Distribution Model that will indicate the Import Name to use. The Import Name, defined in the Import Definition form, defines the source data that will be imported.

Configure the Export Rules for SAP HR Exports If you need to send payroll data to SAP HR, you will need to define the rules and rulesets for determining Wage Types and Attendance/Absence Types. For example, the SAP_ATT_ABS01 export uses the SAP_WAGE_TYPE_RULESET to determine the ABS_ATT_TYPE to export to SAP. Use the ExportRuleset context in the Calc Rule and Rulesets forms to define these rules. The SAP_WAGE_TYPE_RULESET (mentioned in the above example) is a system-defined Export Ruleset. It is recommended that you copy/modify the system-defined rulesets before using them in your Export Definitions.

Configure the Export Definitions for SAP The Export Definition form (Main Menu > Configuration > Interfaces > Export Definition) is used to define the export records for data you are exporting to SAP. To export data from AutoTime to SAP, the OUT_SAP service will search for transactions that are eligible to be sent to SAP. The service puts this data in the Out XML Queue form (interface_out_xml_queue table). It then converts the Out XML Queue (interface_out_xml_queue table) data into an IDOC format, and places the data in the Interface Out Queue form (interface_out_queue table). The OUT_SAP service uses its SENDER_NAME and TRANSACTION_GROUP parameters to look up a record in the Distribution Model that will indicate the Export Name to use. The Export Name, defined in the Export Definition form, defines the source data that will be exported. Once the data is in the interface_out_queue table, it can be converted by the OUT_FILE_WRITER service to an XML file to be read by B-COMM ERP. The Export Definitions for SAP need to use the Export Type XML. This Export Type will export data to an XML file that will produce an XML file that is specific to the ERP XML format and can be used to send data to an ERP system (e.g., SAP). AutoTime comes with several pre-defined Export Definitions for SAP. It is recommended that you copy the system-defined Export Definitions and use the duplicate versions, which can be modified as necessary. SAP_ATT_ABS01 – Use this Export Definition to send payroll data including attendance/absence types to SAP with no dollars. SAP_ATT_ABS_WITH_COST01 – You can also use this Export Definition to send payroll data including attendance/absence types to SAP with no dollars (similar to SAP_ATT_ABS01). However, this Export Definition includes additional elements to export (Company Code, Business Area, Cost Center, etc.). SAP_CONF21 – Use this Export Definition to send labor for Production Planning Orders/Operations to SAP. SAP_CONF32 – Use this Export Definition to send labor for Plant Maintenance Orders/Operations to SAP. SAP_CONF42 – Use this Export Definition to send labor for Project Systems Orders/Operations to SAP. SAP_REM_SPEC01 – Use this Export Definition to send payroll data including wage types to SAP along with the dollar value. SAP_REM_SPEC_WITH_COST01 – You can also use this Export Definition to send payroll data including wage types to SAP along with the dollar value (similar to SAP_REM_SPEC01). However, this Export Definition includes additional elements to export (Company Code, Business Area, Cost Center, etc.).

Configure the Interface Host The Interface Host form (Main Menu > Configuration > Interfaces > Interface Host) is used to define the senders and receivers in the Distribution Model form. Your SAP and B-COMM ERP systems need to be defined in this form. AutoTime comes with several pre-defined Interface Hosts for SAP. It is recommended that you copy the system-defined Interface Hosts and use the duplicate versions, which can be modified as necessary.



Configure the Process Policy The Process Policy form (Main Menu > Configuration > Policies > Process Policy) is used to determine the Sender Name for a transaction’s export process. The Sender Name is used by the OUT_SAP service to determine which data to select from the transaction tables. The Sender Name is defined in the Interface Host form (above). The OUT_SAP service uses the Sender Name in a Process Policy to determine which data to select from the transaction tables. The service then places this export data in the interface_out_xml_queue and interface_out_queue tables, where it can be converted (by the OUT_FILE_WRITER service) to an XML file to be read by B-COMM ERP. B-COMM ERP is the application that is used to exchange data between AutoTime and SAP. AutoTime comes with a predefined Process Policy for SAP. It is recommended that you copy this policy and use the duplicate version, which can be modified as necessary.



Configure the Distribution Model The IN_SAP and OUT_SAP services use the Distribution Model to determine which Import or Export Definition to run. These services use their SENDER_NAME and TRANSACTION_GROUP parameters to look up the Import Name or Export Name in the Distribution Model. You need to define the Sender Name, Receiver Name, and Import Name or Export Name for the SAP import or export you want to run. For example, for the CONF21 transaction, you need to set the Sender Name to the B-COMM ERP system you defined in the Interface Host form. Likewise, you need to set the Receiver Name to the SAP system you defined in the Interface Host form. The IN_SAP service uses its SENDER_NAME and TRANSACTION_GROUP parameters to look up a record in the Distribution Model that will indicate the Import Name to use. The Import Name defines the source data that will be imported from the interface_in_queue tables into the charge_element table. The application comes with predefined Distribution Model records for importing and exporting SAP data. It is recommended that you copy these records and use the duplicate versions, which can be modified as necessary.



Configure the Service Instances You need to configure the following service instances to import and export data with SAP using IDOCs. Import: The B-COMM ERP application receives IDOCs from SAP and processes them into XML files that can be read by AutoTime. The IN_FILE_WRITER service processes the B-COMM ERP files and places them in the Interface In Queue form (interface_in_queue table). You will need to create a link from the B-COMM ERP folder to the Kaba \import folder so that the IN_FILE_WRITER service can process the files. The IN_SAP service converts the IDOC data that is in the in the Interface In Queue form (interface_in_queue table) into a format that AutoTime can read. It then places this data in the in the In XML Queue form (interface_in_xml_queue table). Finally, the IN_SAP service imports the appropriate data from the interface_in_xml_queue tables and into the Charge Element form (charge_element table). Export: The OUT_SAP service will search for transactions that are eligible to be sent to SAP. The service puts this data in the Out XML Queue form (interface_out_xml_queue table). It then converts the Out XML Queue (interface_out_xml_queue table) data into an IDOC format, and places the data in the Interface Out Queue form (interface_out_queue table). Once the data is in the interface_out_queue table, it can be converted by the OUT_FILE_WRITER service to an XML file to be read by B-COMM ERP. B-COMM ERP is the application that is used to exchange data between AutoTime and SAP. You will need to create a link from the B-COMM ERP folder to the Kaba \export folder so that the OUT_FILE_WRITER service can process the files.

Supported IDOCs AutoTime to SAP: ATT_ABS01 = Used to send payroll data including attendance/absence types to SAP with no dollars. ATT_ABS01_WITH_COST01 = Similar to ATT_ABS01. Also used to send payroll data including attendance/absence types SAP with no dollars. However, this IDOC contains additional elements (Company Code, Business Area, Cost Center, etc.). CONF21 = Labor for the Production Planning Order/Operation, which originated from OPERA2 (see below). CONF32 = Labor for the Plant Maintenance Order/Operation, which originated from OPERA3 (see below). CONF42 = Labor for the Project Systems Order/Operation, which originated from OPERA4 (see below). REM_SPEC01 = Used to send payroll data including wage types to SAP along with the dollar value. REM_SPEC01_WITH_COST01 = Similar to REM_SPEC01. Also used to send payroll data including wage types to SAP along with the dollar value. However, this IDOC contains additional elements (Company Code, Business Area, Cost Center, etc.). SAP to AutoTime: HRCC1DNCOSTC = Cost Centers. Maps to AutoTime Charge Type COST_CENTER. HRCC1DNINORD = Internal Orders. Maps to AutoTime Charge Type INTERNAL_ORDER. HRCC1DNWBSEL = WBS Elements. Maps to AutoTime Charge Type WBS_ELEMENT. HRMD_A06 (with Message Type HRMD_A) = Human Resources data. Maps to AutoTime’s Person, Person Assignment, Person Group, and Hierarchy tables. OPERA2 = Production Planning Order. Maps to AutoTime Charge Type ORDER. OPERA3 = Plant Maintenance Order. Maps to AutoTime Charge Type MAINTENANCE_ORDER. OPERA4 = Project Systems Order. Maps to AutoTime Charge Type PROJECT_ORDER. WORKC2 = Production Planning Work Centers. Maps to AutoTime Charge Type ORDER_WORKCENTER WORKC3 = Production Planning Work Centers. Maps to AutoTime Charge Type MAINTENANCE_ORDER_WORKCENTER. WORKC4 = Project Systems Work Centers. Maps to AutoTime Charge Type PROJECT_ORDER_WORKCENTER.

Smile Life

When life gives you a hundred reasons to cry, show life that you have a thousand reasons to smile

Get in touch

© Copyright 2015 - 2024 PDFFOX.COM - All rights reserved.