ERP Simulated Delivery Export

Last modified by Peter Karlsson on 2025/10/03 08:57

Format

Text file, tab-separated values. Number of columns is 11.

Contents

The export file contains order products with status Produced.

After the export elements are signed as exported (IMP_CAST_PLANNING.IsReported2 = 1)

Configuration

<!-- Exported file destination-->
<add key="ERPDeliveryDirectory" value="C:\IMPACT\StruSoft\ERPDelivery\Out" />

<!-- The pattern below is used by simulated delivery export to SAP (param:32)  to exclude projects -->
<add key="ERPDeliveryProjectPrefixExclude" value="^\s{3}P6[0-9]\d{6}" />
<!-- ^\s{3}: Ensures the string starts with exactly three spaces.-->
<!--P: Matches the literal character "P".-->
<!--6[0-9]: Matches any number from 60 to 69.-->
<!--\d{6}: Matches the remaining six digits to complete the 6-digit sequence.-->

<!-- The value below is used by delivery export to SAP (param:2). If it is missing or set to No (default) then it works as the old way -->
<!-- If it is set to YES then the function will not export the element if it is already exported by  -->
<!-- simulated delivery export to SAP (param:32). ie. Imp_Cast_Planning.IsReported2=1 -->

<add key="EnableSimulatedDeliveryExport" value="YES" />    

Export Files Generated

Here is an example.

File name: INT_SE97GoodsIssueDld_20250728_125725.txt

Sales OrderItemNr1MatFactoryQuantityUnitProjectElement MarkDelivery Note IdDateIdentifier
TSP69099999TSP69099999-342000 SEZS4.00M2P69099999E 2025-07-28P69099999-1
TSP69099999TSP69099999-342000 SEZS4.00M2P69099999E 2025-07-28P69099999-2

Column Description

Column NoDescription
1Sales Order Name
2ItemNr1
3Empty
4Factory (e.g. SXXX)
5Quantity
6Unit
7Project
8Element Mark
9Delivery Note Id (Empty)
10Current Date
11Row identifier (Project-Element id)

Details

When the ERP simulated delivery export is triggered the following happens:

  1. The system collects all produced elements that are not yet exported to the ERP system (IMP_CAST_PLANNING.IS_REPORTED2 = 0)
  2. This export is limited to project names that fulfills the pattern given in the config file flag ERPDeliveryProjectPrefixExclude
  3. The elements are grouped by the production factory external name of each element 
  4. A file is created for each group
  5. After the export the reported flag is set (IMP_CAST_PLANNING.IS_REPORTED2 = 1)
  6. Elements with IMP_CAST_PLANNING.IS_REPORTED2 = 1 are excluded from the delivery export to the SAP system if the config file flag EnableSimulatedDeliveryExport is set YES

Sample Exports

Please note the order from top and downward.

Param32 (Simulated Delivery Export to SAP)         
Sales OrderItemNr1MatFactoryQuantityUnitProjectElement MarkDelivery Note IdDateIdentifier
TSP69099999TSP69099999-342000 SEZS4.00M2P69099999E 2025-07-29P69099999-1
TSP69099999TSP69099999-342000 SEZS4.00M2P69099999E 2025-07-29P69099999-2
           
Param2 (Delivery Export to SAP) using <add key="EnableSimulatedDeliveryExport" value="YES" />     
Sales OrderItemNr1MatFactoryQuantityUnitProjectElement MarkDelivery Note IdDateIdentifier
TS800EXT391007 SEZS2STTS_TEST800MP170152560482025-07-29TS_TEST800-41532
TS800EXTTS800EXT-342000 SEZS1.00M2TS_TEST800E70152560482025-07-29TS_TEST800-80
TS800EXTTS800EXT-342000 SEZS1.00M2TS_TEST800E70152560482025-07-29TS_TEST800-81
TS800EXTTS800EXT-342000 SEZS1.00M2TS_TEST800E70152560482025-07-29TS_TEST800-82
           
Param2 (Delivery Export to SAP) using <add key="EnableSimulatedDeliveryExport" value="No" />     
Sales OrderItemNr1MatFactoryQuantityUnitProjectElement MarkDelivery Note IdDateIdentifier
TSP69099999TSP69099999-342000 SEZS4.00M2P69099999E70152560552025-07-29P69099999-1
TSP69099999TSP69099999-342000 SEZS4.00M2P69099999E70152560552025-07-29P69099999-2