PRC_INT_ITEM_ADAPT_NET_VALUE SAP Function module - Anpassen Positionsnettowert (Meilensteinfakturierung)

PRC_INT_ITEM_ADAPT_NET_VALUE is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name PRC_INT_ITEM_ADAPT_NET_VALUE into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: PRC_INT
Released Date: Not Released
Processing type: Normal fucntion module

Pattern for FM PRC_INT_ITEM_ADAPT_NET_VALUE - PRC INT ITEM ADAPT NET VALUE

CALL FUNCTION 'PRC_INT_ITEM_ADAPT_NET_VALUE' "Anpassen Positionsnettowert (Meilensteinfakturierung)
  EXPORTING
    iv_bal_log =                " balloghndl    Anwendungs-Log: Handle eines Protokolls
    iv_item_no =                " prct_item_no  Positionsnummer
    iv_netvalue_orig =          " prct_cond_value  Preisfindung: Konditionswert
    iv_netvalue_new =           " prct_cond_value  Preisfindung: Konditionswert
    iv_milestone_factor =       " prct_milestone_factor  Faktor für Meilensteinfakturierung
  IMPORTING
    es_profile =                " prct_profile  Profil des API-Aufrufes
  CHANGING
    ct_cond =                   " prct_cond_du_tab  interner Tabellentyp für Preisfindungskonditionen
    .  "  PRC_INT_ITEM_ADAPT_NET_VALUE

ABAP code example for Function Module PRC_INT_ITEM_ADAPT_NET_VALUE

The ABAP code below is a full code listing to execute function module PRC_INT_ITEM_ADAPT_NET_VALUE including all data declarations. The code uses the latest in-line data DECLARATION SYNTAX but I have included an ABAP code snippet at the end to show how declarations would look using the original method of declaring data variables up front. This will allow you to compare and fully understand the new inline method. Please note some of the newer syntax such as the @DATA is not available until a later 4.70 service pack (SP8).

DATA:
ld_es_profile  
 
 TYPE PRCT_PROFILE
.


DATA(ld_ct_cond) = 'Check type of data required'.

DATA(ld_iv_bal_log) = 'Check type of data required'.

DATA(ld_iv_item_no) = 'Check type of data required'.

DATA(ld_iv_netvalue_orig) = 'Check type of data required'.

DATA(ld_iv_netvalue_new) = 'Check type of data required'.

DATA(ld_iv_milestone_factor) = 'Check type of data required'.
.

CALL FUNCTION 'PRC_INT_ITEM_ADAPT_NET_VALUE'
  EXPORTING
    iv_bal_log =                 ld_iv_bal_log
    iv_item_no =                 ld_iv_item_no
    iv_netvalue_orig =           ld_iv_netvalue_orig
    iv_netvalue_new =            ld_iv_netvalue_new
    iv_milestone_factor =        ld_iv_milestone_factor
  IMPORTING
    es_profile =                 ld_es_profile
  CHANGING
    ct_cond =                    ld_ct_cond
    .  "  PRC_INT_ITEM_ADAPT_NET_VALUE

IF SY-SUBRC EQ 0.
  "All OK
ENDIF.

ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:

ld_ct_cond
 
 TYPE PRCT_COND_DU_TAB ,
ld_es_profile
 
 TYPE PRCT_PROFILE ,
ld_iv_bal_log
 
 TYPE BALLOGHNDL ,
ld_iv_item_no
 
 TYPE PRCT_ITEM_NO ,
ld_iv_netvalue_orig
 
 TYPE PRCT_COND_VALUE ,
ld_iv_netvalue_new
 
 TYPE PRCT_COND_VALUE ,
ld_iv_milestone_factor
 
 TYPE PRCT_MILESTONE_FACTOR .


ld_ct_cond = 'Check type of data required'.
ld_iv_bal_log = 'Check type of data required'.
ld_iv_item_no = 'Check type of data required'.
ld_iv_netvalue_orig = 'Check type of data required'.
ld_iv_netvalue_new = 'Check type of data required'.
ld_iv_milestone_factor = 'Check type of data required'.