Documentation View

We are hiring and constantly growing! Have a look through our vacancies to find the right role for you!

/PM0/ABT_APIF_REL_FB - Create and Process New Business Application (Application Interface)

/PM0/ABT_APIF_REL_FB - Create and Process New Business Application (Application Interface)

SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   RFUMSV00 - Advance Return for Tax on Sales/Purchases  
This documentation is copyright by SAP AG.
SAP E-Book

Functionality

Function

FS-PM uses the APIF (application interface) to provide an RFC-enabled interface to create and release applications.

The APIF cannot update the data of an existing application.

The application interface allows you to levy general business transaction charges for the following business transactions in the New Business business process:

  • Create and Process Contract
  • Create and Process Coverage
  • Create and Process Coverage Package
  • Create and Process Subcoverage
  • Process Policy
  • Create Contract Package

It also enables you to levy a premium charge for the Create and Process Contract business transaction, creditor charge, and correspondence charge.

These charges are determined and levied automatically according to the system settings. You cannot manually change the charges.

The interface provides the following functions:

  • Additional Key for Contract Lock - IV_LOCKKEY_ID

To map various application scenarios, some of the described functions are optionally executable, for instance Simulate Commission Settlement, however they may be prerequisites of each other, for instance no release without prior calculation. This is explained in the application scenarios listed below and also in the documentation of the available indicators in the 'Dependency' section.

The behavior of the APIF with regard to the business functions described above can be controlled at the technical level:

Call

Particular attention was paid to runtime considerations in the development of the APIF. It applies the concept of data containers, which are processed in background processing with improved performance (IF_MASS_BO indicator). Therefore, the application data should usually be transferred in two stuctures/tables per entity, one table for the application data and one table for the field modifiers. The field modifiers note which data of the transferred table should be used in processing.

If processing is successful, the policy application numbers resulting from creation are transferred to the caller, or in the event of errors log messages are transferred for handling errors.

Enhanceability

The APIF is based on structures of the UBOI (Unified Business Object Interface) that generally contain a customer include, which makes them enhanceable. Data can also be transferred as ExtensionIn parameters, which can be checked in /PM0/ABT_APIF_CHECK_BADI. You can use the BAdI /PM0/ABT_CHK_EXISTING_POL to adjust the idempotence check to your specific requirements.

Example

Application Scenarios Without Idempotence Indicator Being Set

Scenario 1: Creation and Calculation Without Release

  • Application data is free of errors.
  • Parameters:
  • IF_BO = 'X'

  • IF_CALC = 'X'

  • Application is calculated and saved.

Scenario 2 - Creation and Release

  • Application data is free of errors.
  • Parameters:
  • IF_BO = 'X'

  • IF_CALC = 'X'

  • IF_APPROVE = 'X'

  • => Application is created, calculated, saved, and released.

Scenario 3: Creation in Event of Errors Without Saving in Event of Errors

  • Application data contains errors.
  • Parameters:
  • IF_BO = 'X'

  • IF_CALC = 'X'

  • IF_APPROVE = 'X'

  • IF_SAVE_ON_ERRORS = Not set

  • => Error message: Application with errors will not be saved.
  • => Application must be sent again with corrected data.

Scenario 4: Creation In Event of Errors With Saving In Event of Errors

  • Application data contains errors.
  • Parameters:
  • IF_BO = 'X'

  • IF_CALC = 'X'

  • IF_APPROVE = 'X'

  • IF_SAVE_ON_ERRORS = 'X'

  • => Error message: Application with errors will be saved.
  • => Application can be sent again (with corrected data); in this case a new application is created and the existing application cannot be updated.
  • => Processing of existing application can be resumed in Central Access (/PM0/ABC_FSPM).

Application Scenarios With Idempotence Indicator Being Set

Scenario 1: Creation with new external application number with release

  • Application data is free of errors.
  • Parameters:
  • IF_IDEMPOTENCE = 'X'

  • IF_BO = 'X'

  • IF_CALC = 'X'

  • IF_APPROVE = 'X'

  • => Application is created and released.

Scenario 2: Creation using existing external application number with release

  • Application data is free of errors.
  • Parameters:
  • IF_IDEMPOTENCE = 'X'

  • IF_BO = 'X'

  • IF_CALC = 'X'

  • IF_APPROVE = 'X'

  • => Information message: Policy or application already exists.
  • => Processing of existing application can be resumed in Central Access (/PM0/ABC_FSPM).

Scenario 3: Creation Without External Application Number Without Release

  • Application data is free of errors.
  • Parameters:
  • IF_IDEMPOTENCE = 'X',

  • IF_BO = 'X'

  • IF_CALC = 'X'

  • => Error message: Application will not be created since no application number was specified.

Scenario 4: Creation with Existing External Application Number Without Release

  • Application data is free of errors.
  • Parameters:
  • IF_IDEMPOTENCE = 'X',

  • IF_BO = 'X'

  • IF_CALC = 'X'

  • => Information message: Policy or application already exists.
  • => The application will not be saved.
  • => Processing of existing application can be resumed in Central Access (/PM0/ABC_FSPM).

Scenario 5: Creation in Event of Errors Without Saving in Event of Errors

  • Application data contains errors.
  • Parameters:
  • IF_IDEMPOTENCE = 'X'

  • IF_BO = 'X'

  • IF_CALC = 'X'

  • IF_APPROVE = 'X'

  • IF_SAVE_ON_ERRORS = Not set

  • => Error message: Application with errors will not be saved.
  • => Application can be resent (if applicable, with the same external application number).

Scenario 6: Creation In Event of Errors With Saving In Event of Errors

  • Application data contains errors.
  • Parameters:
  • IF_IDEMPOTENCE = 'X'

  • IF_BO = 'X'

  • IF_CALC = 'X'

  • IF_APPROVE = 'X'

  • IF_SAVE_ON_ERRORS = 'X'

  • => Error message: Application with errors will not be saved.
  • => Application can be resent (if applicable, with the same external application number).

Notes

Further information





Parameters

APPLNR
ERRORCODE
EXTENSIONIN
IF_APPROVE
IF_BO
IF_CALC
IF_CHECK
IF_CHECK_ADVANCED
IF_COMM
IF_CREATE_APPL_DFS
IF_IDEMPOTENCE
IF_MASS_BO
IF_REQ_CBC
IF_SAVE
IF_SAVE_ON_ERROR
IT_AAWACOV
IT_AAWAPOLPR
IT_AAWFCOV
IT_AAWFPOLPR
IT_ABEACS
IT_ABUTTRANS
IT_ABWAAGENT
IT_ABWAANSWER
IT_ABWAAPPLPOL
IT_ABWABNFCRY
IT_ABWACBCPAYR
IT_ABWACLAUSE
IT_ABWACOMDIFF
IT_ABWACOMMIS
IT_ABWACOMROLE
IT_ABWACOVCPCO
IT_ABWACOVPAC
IT_ABWACRDITOR
IT_ABWADEDCTBL
IT_ABWADEDSRCL
IT_ABWADIACODE
IT_ABWAEDISTREL
IT_ABWAEXREF
IT_ABWAEXTPCL
IT_ABWAEXTPOL
IT_ABWAINFRD
IT_ABWALIMIT
IT_ABWAPOLHLDR
IT_ABWAPOLICY
IT_ABWAPPDPAC
IT_ABWAPRMPAYR
IT_ABWAREPVAL
IT_ABWARESDEPC
IT_ABWASBADR
IT_ABWASUBJCT
IT_ABWASUPDC
IT_ABWDCOINCO
IT_ABWDCOINHS
IT_ABWDCOINSS
IT_ABWFAGENT
IT_ABWFANSWER
IT_ABWFBNFCRY
IT_ABWFCBCPAYR
IT_ABWFCLAUSE
IT_ABWFCOINCO
IT_ABWFCOINHS
IT_ABWFCOINSS
IT_ABWFCOMDIFF
IT_ABWFCOMMIS
IT_ABWFCOMROLE
IT_ABWFCOVCPCO
IT_ABWFCOVPAC
IT_ABWFCRDITOR
IT_ABWFDEDCTBL
IT_ABWFDEDSRCL
IT_ABWFDIACODE
IT_ABWFEDISTREL
IT_ABWFEXREF
IT_ABWFEXTPCL
IT_ABWFEXTPOL
IT_ABWFINFRD
IT_ABWFLIMIT
IT_ABWFPOLHLDR
IT_ABWFPOLICY
IT_ABWFPPDPAC
IT_ABWFPRMPAYR
IT_ABWFREPVAL
IT_ABWFRESDEPC
IT_ABWFSBADR
IT_ABWFSUBJCT
IT_ABWFSUPDC
IT_ALWAADDPRPY
IT_ALWAASFUND
IT_ALWABNF
IT_ALWAINDINC
IT_ALWAPPDSTL
IT_ALWAPREM
IT_ALWASUBSAG
IT_ALWAVALID
IT_ALWFADDPRPY
IT_ALWFASFUND
IT_ALWFBNF
IT_ALWFINDINC
IT_ALWFPPDSTL
IT_ALWFPREM
IT_ALWFSUBSAG
IT_ALWFVALID
IT_ANSWERS
IT_NOTES_APIF
IV_LOCKKEY_ID
KEY_MAPPING
MESSAGES
POLICYNR

Exceptions

/PM0/CX_3FT_EXCEPTION

Function Group

/SAPLABT_APIF

SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   ROGBILLS - Synchronize billing plans  
This documentation is copyright by SAP AG.

Length: 24041 Date: 20211129 Time: 190919     sap01-206 ( 150 ms )