How to define WE20 partner for all outb deliveries

Question

Hello, I would like to create an outbound delivery DELVRY05 IDoc for every delivery.   When the warehouse (LIKP-LGNUM) is a certain value, and the packing status is 'C', we'd like to produce the IDoc and save to a file port.   I have setup most of this, but am stuck on the partner function settings.   In NACE, I have defined a new output type 'ZAWB' under V2.  I have select 'EDI' for the medium.  But on the Default Values tab, what should the partner function be?   I want this for all customers.  I can't go and create a WE20 entry under 'KU' for every single customer.  Also in NACE, does an entry need to exist in the Partner Functions screen?  And how would the WE20 partner be defined?

Answer 1

Requirement:
Produce an outbound IDoc containing delivery data.  When the delivery
header packing status = 'C' AND the warehouse is 'SHN' 'SRV' or 'OCE',
the output should appear in the Extras -> Delivery Output -> Header screen
as a new entry.  The output will produce a DELVRY05 IDoc, message type DESADV.
It will be saved as a file on the SAP server, formatted in XML format.
Setup to get this to work:
Since the warehouse number LIKP-LGNUM was not available in the standard
communication structure KOMKBV2, the field needed to be added so we can
use it in an output condition record.
1.  Structure ZAKOMKBZ4, added field ZZLGNUM for warehouse number.
    This structure is an include in communication structure KOMKBV2.
2.  Added field ZZLGNUM to structure ZAKOMBZ, which is included in
    structures KOMB and KOMBZ.  Needed to update the Field Catalog.
3.  Edited program RVCOMFZZ, Form USEREXIT_KOMKBV2_FILL
    to move the warehouse value from LIKP into the communication structure.
    Insert the code:   COM_KBV2-ZZLGNUM = COM_LIKP-LGNUM.
4.  Add field ZZLGNUM to Field Catalog, table V_T681F.  Use SM30
    Usage: B    Appl: V2    Field Group: 001
    This will also add an entry to table T681F
5.  v/59   V/60   v/61   Create/Change/Display Condition Table (Output Shipping)
    With SE11, see what table number is avail, put B9* and hit F4. 923 wasn't being used yet.
    Used v/59 to create new condition table 923.   
    Warehouse should appear on the right side now if you did steps above.
    Add field to the left side: Warehouse  (just dbl-click Warehouse on the right side and it should
appear on the left)
    Pressed 'Generate' button and it created table B923
6.  Txn NACE.  Select row V2, then click  Access Sequence button.
    Created new Access Sequence Z005 'Warehouse'
    Select row Z005 and dbl-click Access, Add new row: Access Nbr: 10  Table: 923   Hit Save.
    Hit Back once and select row Z005 again and dbl-click Fields, which should
    automatically fill in a new row showing the new ZZLGNUM field.  Hit Save.
7.  Txn NACE.  Select row V2, then click  Output Types  button
    Created new output type ZAWB which will be used to produce the DELVRY05 IDoc
    Tabs:                    Field:                Value:
      General Data             Access Sequence       Z005
                               Access to Conditions  checked
      Default Values           Dispatch time         Send immediately                   
                               Transmission Medium   EDI
                               Partner Function      SH    (Ship-To Party)
    Processing Routines:
      Program:       RSNASTED
      Form Routine:  EDI_PROCESSING
    Partner functions:  (1 entry)
      Medium   : EDI      Function:  SH  
8.  Txn BD54.  Created new Logical System 'IEDHL'  for Ireland DHL 3PL Warehouse (Non-SAP)
    This is not really a 'system'.  The plan is to save the IDoc files to a folder on the
    SAP filesystem.
9. VV21  VV22  VV23   Output - Condition Records : Shipping
    But we can get to this as well via txn NACE.
    Create 3 new entries in the condition table.
    Output type     :  ZAWB   (our new output type)
    Key Combination :  Warehouse  (is the only selection)
    Warehouse number:  SHN   (do same for SRV and OCE)
    Function        :  LS
    Partner         :  IEDHL  (this will be populated in the output screen in VL02N)
    Medium          :  6  - EDI
    Date/time       :  4  - Immediate
    Language        :  EN
    Notice the entries appears in the table B923 now, created in step 5.
10.  Output the IDoc in XML format.  In WE21, define a port under XML file.  I will
     call it DEV_XML.  On the Outbound file tab, you can specify a function module
     that is used to create the filename.  For example, EDI_PATH_CREATE_CLIENT_DOCNUM.
11. Txn WE20.  Under Partner Type  'LS', Add partner 'IEDHL'.
    Then create an outbound parameter for DESADV as follows:
    Partner No.   :  IEDHL
    Partner Type  :  LS
    Partner Role  :  LS
    Message Type  :  DESADV
    Tabs:                    Field:                 Value:
      Outbound Options         Receiver Port          DEV_XML  (Define with WE21)
                               Transfer IDoc Immed.   (selected)
                               Do not start subsys    (selected)
                               Basic Type             DELVRY05
                               Canc Proc after Err    (checked)
                               Segm. Release in IDoc  700
      Message Control          Application            V2
                               Message Type           ZAWB
                               Process Code           DELV
      Perm. Agent              Type                   O         (or US)
                               Agent                  50000079  (or your username)
                               Language               EN