Page tree
Skip to end of metadata
Go to start of metadata

Purpose

This page explains the standard behavior while creating follow on RFx of preceding RFx. 

Overview

1. Situation 1 

2. Situation 2

3. Behavior 

4. Solution 

Situation 1 

If you maintained more than one transaction type in the configuration table, system takes the original transaction type from follow up RFx. 

Situation 2

If you have more than one transaction type in the configuration table, system does not pop-up select screen to choose a different transaction type from customizing 

Behavior

When we create a follow-on RFx, the system will search from the customizing the follow-on transaction type. In case there are more than one, system will take the original one.

  

Solution

It is possible to use BADI BBP_DOC_CHANGE in order to assign the corresponding transaction type according to some parameters.

The following code determines the transaction type of the new resulting Rfx:

/SAPSRM/CL_PDO_BO_RFQ

/SAPSRM/IF_PDO_BO_RFQ~ACTION_CREATE_FOLLOW_ON_RFQ

* Check the successors

  LOOP AT lt_successors INTO ls_succ WHERE object_type EQ/sapsrm/if_pdo_obj_types_c=>gc_pdo_biddingdoc.

    lv_count = lv_count + 1.

    IF lv_count EQ 1.

      lv_next_proc_type = ls_succ-process_type.

    ELSE.

      lv_next_proc_type = mv_process_type.

      CONTINUE.

    ENDIF.

  ENDLOOP.