The documentation from version 39.5.17 of PLANTA project can be found in the new PLANTA Online Help.

ERP Export Up to S 39.5.4

From server version 39.5.4, PLANTA provides PLANTA link, a universal interface which replaces the previous ERP interface. For this purpose, see Universal Interface.

Presettings

  • The settings for the file to which is imported are defined in the technical (indirect) 009BTE ERP Hours Export and 009BTF ERP Cost Export modules.
  • If individual settings are required by the customer (regarding filter, summarization, structure etc.) the modules mentioned above have to be adjusted.
  • Please consider that the sequence of data fields in the modules (data areas) corresponds to the sequence in the file.
    • Data field 1 in the module = column 1 in the file etc.

Information

  • The export runs in two steps.
    • In the first step, the data from the PLANTA load table (DT472) is copied to the intermediate table (DT591).
    • In the second step, the data is exported from the intermediate table to a file.
Procedure
  • Step 1
    • In the Date from and Date to fields, enter the period for which the load records are to be exported.
      • If you activate the Set key date checkbox, the date from the Date to field is transferred to the model parameters as the key date.
    • Click on the Data from DT472 button.
      • Now, the data from DT472 Load is copied to DT591 Pool Table
        • In the standard system, the settings for transfer of data from DT472 to the pool table are saved in the technical SAP: Data from DT472 (009BPF) module. By default, all records of the selected period are copied to the pool table. This setting can be changed to meet the customer's requirements.
      • For the load records copied to the DT591, a transaction header is created in DT590 for each transaction.
      • As soon as the load records from DT472 are copied to DT591, they receive SAP status = 1 (Prepared for transfer to SAP) in both tables.
        • As a result, the records are locked in DT472 and reported actual dates cannot be changed anymore. Corrections can only be made by reverse postings.
  • Step 2
    • In the Server export path and Client export path fields, you can define the destination where the file should be exported.
      • In the standard, for the server/client path and the file names, the presettings from the Global settings are taken.
    • When you click on one of the three buttons, data from DT591 is exported to the defined target file.
      • The settings for the data transfer is saved in the modules mentioned above. In the standard it is preset by default that only records with resource type = 1* and 2 are transfered when you click on the Export Hours button. When you click on the Export Costs button, only records with resource type = 9 are transferred and when you click on the Cost and Hours Export button, the settings of both modules are considered. These settings can be changed to meet the customer's requirements.
      • For the transfer, it is relevant whether the Test export checkbox is activated or not.
        • If the checkbox is activated (default setting), the export can be run several times for test purposes. As a result, all records in DT472 and DT591 are assigned the SAP status = 5 (File export).
        • Is the checkbox deactivated, it is a true export. All records are finally transferred to the file and receive SAP status 2 (Transferred successfully to SAP) in DT472 and 591.

Note

  • The data exported from the DT472 cannot be changed afterwards via the corresponding modules (e.g. Work Reporting). If you try to do so, an error message appears.

         PLANTA project









 
  • Suche in Topic-Namen

  • Suche in Topic-Inhalten
This site is powered by the TWiki collaboration platform Powered by Perl