Fonction SAP BAPI_CD_INSOBJ_CREATE - OBSOLETE: Use BAPI_INSOBJECT_CREATE

Paramètre Reférence Type Long. Valeur par déf. Facultatif Description
INSOBJECTDATA BAPICD_INSOBJ u 77 FS-CD: BAPI Structure for Insurance Object Data (Creation)
INSOBJECTDATAX BAPICD_INSOBJX u 4 FS-CD: BAPI Change Structure for IO Data (Creation)
NODATA BAPI_CD_INSOBJ_CONTROL-NODATA C 1 '/' X NODATA Indicator
TESTRUN BAPICTRACAUX-TESTRUN C 1 X Switch to Simulation Mode for Write BAPIs
WRITECHANGEDOCUMENTS BAPI_CD_INSOBJ_CONTROL-WRITECHANGEDOCUMENTS C 1 'X' X Indicates Whether Change Documents Are to Be Created

Paramètre Reférence Type Long. Description
INSOBJECTNUMBER BAPICD_INSOBJ-INSOBJ_NUMBER C 20 Identification for an Insurance Object

Paramètre Reférence Long. Facultatif Description
EXTENSIONIN BAPIPAREX 990 X Reference Structure for BAPI Parameters EXTENSIONIN/EXTENSIONOUT
INSOBJECTPARTNER BAPICD_INSOBJ_PARTNER 705 FS-CD: BAPI Structure for IO Partner Data (Creation)
INSOBJECTPARTNERBRKASSGN BAPICD_INSOBJ_PARTNER_BRK_A 113 X FS-CD: BAPI Structure IO Partner Broker Assignment (Creation)
INSOBJECTPARTNERBRKASSGNX BAPICD_INSOBJ_PARTNER_BRK_AX 10 X FS-CD: BAPI Change Structure IO Partner Broker Assignment (Creation)
INSOBJECTPARTNERBROKER BAPICD_INSOBJ_PARTNER_BROKER 97 X FS-CD: BAPI Structure Insurance Object-Partner Broker Data
INSOBJECTPARTNERBROKERX BAPICD_INSOBJ_PARTNER_BROKERX 17 X FS-CD: BAPI Change Structure IO Partner Broker Data
INSOBJECTPARTNERCORR BAPICD_INSOBJ_PARTNER_CORR 74 X FS-CD: BAPI Structure IO Partner Correspondence Data
INSOBJECTPARTNERCORRX BAPICD_INSOBJ_PARTNER_CORRX 9 X FS-CD: BAPI Change Structure IO Partner Correspondence Data
INSOBJECTPARTNERLOCK BAPICD_INSOBJ_PARTNER_LOCK 107 X FS-CD: BAPI Structure Insurance Object-Partner Lock Data
INSOBJECTPARTNERLOCKX BAPICD_INSOBJ_PARTNER_LOCKX 15 X FS-CD: BAPI Change Structure IO Partner Lock Data
INSOBJECTPARTNERPAY BAPICD_INSOBJ_PARTNER_PAY 149 X FS-CD: BAPI Structure for Ins. Obj. Outg. Payment Data
INSOBJECTPARTNERPAYX BAPICD_INSOBJ_PARTNER_PAYX 16 X FS-CD: BAPI Change Structure for IO Outg. Payment Data
INSOBJECTPARTNERX BAPICD_INSOBJ_PARTNERX 73 FS-CD: BAPI Change Structure for IO Partner Data (Creation)
RETURN BAPIRET2 548 Return Parameter(s)

Functionality
You create an insurance object with this method.

  • You can only create one insurance object within a call.

  • You can assign multiple partners simultaneously to one insurance object.

  • You must assign at least one business partner to the insurance object.
    • You must already have created the business partner in the system.
    • You must assign every insurance object-partner relationship to a
      • contract account. You must already have created the contract account inthe system.
      Exceptions
      If you use account creation variants, an existing contract account isassigned or a new contract account is created.
      Preconditions
      You require the authorization to create insurance objects.
      The RETURN parameter can output more than one message at the same time.
      If you have chosen the Required Entry property in Customizing forcertain field groups for the insurance object, the appropriate fieldsmust be filled.
      If you have defined default values for the appropriate insurance objectcategory in Customizing, these are used if the field is not providedwith a value by the interface. A field is filled with a value if, in thecorresponding structure, the field with the same name and the 'X' suffixcontains an X.

      Notes
      Event V950 is called up within the BAPI. In this event, all datatransferred to the interface can be changed, or missing data can beenhanced.
      The BAPI uses the concept of customer enhancements with BAPI TableExtensions. The EXTENSIONIN parameter exists for this.
      The associated structures are called BAPI_TE_DIMAIOB andBAPI_TE_DIMAIOBPAR. If you want to fill additional defined fields withthe BAPI, you must have implemented these structures.

      Description
      The created insurance object number is returned.

      Description
      Data for insurance object
      You must fill the INSOBJ_NUMBER and INSOBJ_CATEGORY fields.

      Description
      This parameter contains the same field name as the INSOBJECTDATAparameter. For every field that you want to provide with a value in theINSOBJECTDATA structure, you have to fill the corresponding field inthis structure with an 'X'.
      This is necessary to allow the use of the 'SPACE' value.

      Default

      Description
      NODATA flag
      We recommend that you always use the value '/' as the NODATA flag.

      Description
      Flags whether the system is only to simulate the creation of aninsurance object.

      Description
      Flags whether change documents are to be craeted.

      Description
      Parameter for filling additional fields
      You can implement additional fields for the insurance object, as well asfor the insurance object-partner relationship.
      If you want to fill additional fields for the insurance object, you mustset the value 'BAPI_TE_DIMAIOB' in the STRUCTURE field.
      For fields for the insurance object-partner relationship, you must setthe 'BAPI_TE_DIMAIOBPAR' value.
      In the following fields for the EXTENSIONIN parameter, you mustset the values for the items that correspond to the BAPI_TE_DIMAIOB
      or BAPI_TE_DIMAIOBPAR DDIC structures.

      Description
      Data for an insurance object-partner relationship
      You must assign at least one business partner to every insurance object.You must assign more than one business partner at the same time.
      You must assign an account to every insurance object-partnerrelationship. You do this by entering a contract account in theACCOUNT_NUMBER field, or by using an account creation variant inthe ACCT_CREATE_VARIANT field.
      For some fields (such as PARTNER_NUMBER), you have the option ofentering an alternative externally assigned identification number. Thecorresponding fields have '_EXT' as a suffix (as inPARTNER_NUMBER_EXT).

      Description
      Data for the assignment of a broker to an insurance object-partnerrelationship

      Description
      This parameter contains the same field name as theINSOBJECTPARTNERBRKASSGN parameter. For every field, that youwant to provide with a value in the INSOBJECTPARTNERBRKASSGNstructure, you must fill the corresponding field in this structure with'X'.
      This is necessary to be able to use the 'SPACE' value.

      Default

      Description
      Broker Data for an Insurance Object-Partner Relationship
      You must always fill the PROCESSING_MODE field with the value'I'.
      Only use this parameter if you want to create an insurance object fromthe 'Broker Contract' category.

      Description
      This parameter contains the same field name as theINSOBJECTPARTNERBROKER parameter. For every field, that you want toprovide with a value in the INSOBJECTPARTNERBROKER structure, you mustfill the corresponding field in this structure with X.
      This is necessary to be able to use the SPACE value.

      Description
      Data for alternative correspondence recipients for an insuranceobject-partner relationship
      You must always fill the PROCESSING_MODE field with the value 'I'.

      Description
      This parameter contains the same field name as theINSOBJECTPARTNERCORR parameter. For every field, that you want toprovide with a value in the INSOBJECTPARTNERCORR structure, youmust fill the corresponding field in this structure with 'X'.
      This is necessary to be able to use the 'SPACE' value.

      Default

      Description
      Data for business locks for an insurance object-partner relationship

      You must always fill the PROCESSING_MODE field with the value 'I'.
      To create a business lock, you must only fill the fields that have'_KEY' as a suffix.

      • Fill the LOCK_TYPE_KEY field to identify the category of a lock.

        • Lock categories are defined in the TFK080B table. (The lock category
        for locks on the insurance object-business partner relationship is
        always 22.)
        • Fill the PROCESS_ID_KEY field to identify the process for which a
          • lock is set.
          Lock processes for business locks are defined in the TFK080F table.
          Examples for processes:
          01 = Dunning
          02 = Incoming payment
          03 = Outgoing payment
          04 = Interest calculation
          05 = Invoicing
          ...
          • Fill the LOCK_REASON_KEY field to identify the lock reason for a
            • business process.
            A lock reason is entered for more specific description of a lock within
            a business process. Lock reasons can be defined in the IMG
            (Contract Accounts Receivable and Payable -> Business Transactions)
            for each business transaction.

            Description
            This parameter contains the same field name as theINSOBJECTPARTNERLOCK parameter. For every field, that you want toprovide with a value in the INSOBJECTPARTNERLOCK structure, youmust fill the corresponding field in this structure with 'X'.
            This is necessary to be able to use the 'SPACE' value.

            Default

            Description
            Outgoing Payment Data for an Insurance Object-Partner Relationship

            You must always fill the PROCESSING_MODE field with the value 'I'.
            Only use this parameter if you have set the MULT_ALTPAYTREC (multiplepayment recipients active for the contract) flag for the insuranceobject-partner relationship, and have specified an allocation type inthe OUTG_ALLOCTYPE field.

            Description
            This parameter contains the same field name as the INSOBJECTPARTNERPAYparameter. For every field, that you want to provide with a value in theINSOBJECTPARTNERPAY structure, you must fill the corresponding field inthis structure with X.
            This is necessary to be able to use the SPACE value.

            Default

            Description
            This parameter contains the same field name as the INSOBJECTPARTNERparameter. For every field, that you want to provide with a value in theINSOBJECTPARTNER structure, you must fill the corresponding field inthis structure with X.
            This is necessary to be able to use the SPACE value.

            Default

            Description
            Parameter for message output.