SAP Function BAPI_TSW_PART_CREATEFROMDATA - BAPI Function to create TSW Partner

Parameter Reference Type Length Default Optional Text
CARRIERTICKETNUMBERRULE BAPITSWPART08-TICKNUMBERRULE C 3 X OIL-TSW: Ticket number rules
CUSTOMERID BAPITSWPART01-CUSTOMERID C 10 Customer number
IDFORTRANSPORTSYSTEM BAPITSWPART08-PARTNERIDBYTS C 30 X OIL-TSW: Pipeline partner ID
LOCATIONID BAPITSWPART08-LOCATION C 10 OIL-TSW: Location ID
PLANTID BAPITSWPART01-PLANTID C 4 Plant
ROLETYPE BAPITSWPART01-ROLETYPE C 6 OIL-TSW: Role type
STORAGELOCATIONID BAPITSWPART01-STORAGELOCATIONID C 4 Storage location
TRANSPORTSYSTEMID BAPITSWPART08-TRANSPORTSYSTEM C 10 OIL-TSW: Transport system
VENDORID BAPITSWPART01-VENDORID C 10 Account number of vendor or creditor

Parameter Reference Type Length Text
PARTNERDATA BAPITSWPART08 u 266 TSW Partner Role master data (IS-OIL TSW)

Parameter Reference Length Optional Text
EXTENSIONIN BAPIPAREX 990 X Ref. structure for BAPI parameters EXTENSIONIN/EXTENSIONOUT
EXTENSIONOUT BAPIPAREX 990 X Ref. structure for BAPI parameters EXTENSIONIN/EXTENSIONOUT
RETURN BAPIRET2 548 Return parameter


Generated include for enhancement - SCHMIDTCHRI - 31.10.2001
INCLUDE '46C SP1' OBJECT DOKU ID TX LANGUAGE E
IF 'Never Display' = 'True'
ENDIF

Description
TSW Partner Role master data (IS-OIL TSW)

Fields
CUSTOMERID
VENDORID
PLANTID
STORAGELOCATIONID
ROLETYPEE
PARTNERTYPETEXT
ROLETYPEDIFFERNTIATOR
TRANSPORTSYSTEM
TRANSPORTSYSTEMNAME
LOCATIOND
LOCATIONNAME
PARTNERTYPE
COMMONPARTNERID
PARTNERIDBYTS
TICKNUMBERRULE
BLOCKINGINDICATOR
DELTIONINDICATOR

Description
Ticket Number Rules

Description
Customer Number

Description
PARTNERID

Description
LOCATIONID

Description
PLANTID

Definition
A TSW partner role type determines the business function that can becarried out by a partner.

Use
At the present time, the following role types are recognized inconnection with the primary distribution process:

  • TSW001 - Carrier

  • TSW002 - Shipper

  • TSW003 - Supplier

  • TSW004 - Supplier in pipe

  • TSW005 - Receiver

  • TSW006 - Receiver in pipe

  • TSW007 - Consignee

  • TSW008 - Tanker

  • TSW009 - Inspector

  • TSW010 - Breakout storage location - locational

  • TSW011 - Breakout storage location - notional

    • Some of the available TSW role types can be used according to the rolepartner types.


    Role Partner Type : Customer

    • TSW005 - Receiver

    • TSW006 - Receiver in pipe

    • TSW008 - Tanker

      • Role Partner Type : Vendor
      • TSW001 - Carrier

      • TSW002 - Shipper

      • TSW003 - Supplier

      • TSW004 - Supplier in pipe

      • TSW007 - Consignee

      • TSW008 - Tanker

      • TSW009 - Inspector

        • Role Partner Type : Plant
        • TSW003 - Supplier

        • TSW005 - Receiver

        • TSW010 - Breakout storage location - locational

        • TSW011 - Breakout storage location - notional

          • Role partner type : Plant / storage location
          • TSW003 - Supplier

          • TSW005 - Receiver

          • TSW010 - Breakout storage location - locational

          • TSW011 - Breakout storage location - notional

            • Description
            STORAGELOCATIONID

            Description
            TRANSPORTSYSTEMID

            Description
            VENDORID

            Description

            Description
            This parameter can be used to transfer user-specific enhancements tothe BAPI. The customer has to complete the EXTENSIONIN structure andthe system automatically continues processing it.
            The following table extension is available to pass customer-addedfields to the exchange agreement database table OIJRRA:
            Table extension name: BAPI_TE_OIJRRA
            If no user-specific fields or no additional database tables have beendefined by the customer for exchange agreements, the EXTENSIONINparameter can be omitted.
            A table row is made up of the following components:
            STRUCTURE,,Structure name of BAPI table extension (e.g.BAPI_TE_OIJRRA)
            VALUEPART1,,Data part of BAPI extension parameter
            VALUEPART2,,Data part of BAPI extension parameter
            VALUEPART3,,Data part of BAPI extension parameter
            VALUEPART4,,Data part of BAPI extension parameter
            This table allows you to add to the export parameters of the BAPIwithout modifying it.

            • Adapting existing SAP database tables

              • Adding customer-specific fields to SAP tables
              Including existing database fields
              • Including additional customer-specific database tables

                • The following BAPI Table Extension is available:
                • BAPI_TE_OIJRRA

                  • Description
                  Return parameter
                  INCLUDE BAPI_TABLE
                  For information on the meaning of the individual fields in the
                  structure, see the corresponding data element documentation for the
                  individual fields.

                  Value range

                  Type ID Number Message
                  E OD 675 You are not authorized to run this program
                  E OIJ_IF 012 Partner role &1 for obj. &2 &3and differentiator &4 does not exist
                  E OIJ_IF 014 No business object (like customer, vendor;plant/storage loc.) specified
                  E OIJ_IF 015 No TSW master data (like transport system orlocation) specified
                  E OIJ_IF 016 Too many business objects (for example, customerand vendor) specified
                  E OIJ_IF 017 Unexpected error occurred during &1
                  E OD 033 Business object &1 is not valid for roletype &2
                  E OD 034 Role &1 is only relevant to a transportsystem
                  E OD 035 Role &1 is only relevant to a location
                  E OD 036 Role type &1 is relevant to both transportsystem and location
                  E OD 037 OD indicator missing for role type &1
                  E OD 038 Customer &1 does not exist
                  E OD 039 Vendor &1 does not exist.
                  E OD 040 Plant &1 is an in-transit plant
                  E OD 054 TSW location &1 does not exist, or is aninvalid entry for this field
                  E OD 205 Transport system &1 does not exist
                  E OD 607 Plant &1 does not exist
                  E OD 608 Storage location &1 does not exist inplant &2
                  E OD 652 No TS/loc assignment between TS &1 andlocation &2 exists
                  E OD 653 Role type &1 cannot be set fordestination; only location
                  E OD 654 Role type &1 cannot be set for origin;only location
                  E OD 655 Location &1 already has another plant,2, assigned to it
                  E OD 656 Plant &1 has already been assigned tolocation & &2