Skip to Content

Archived discussions are read-only. Learn more about SAP Q&A

making an operand inactive for a given installation...

Hi Gurus,

My requirement is to add the OPERAND pertaining to the installation fact. The values to be set come from workflow.

For example, workflow sends the new operand values for a given installation as

(1) SENIOR

(2) FARM

Currently, I am using Master data template as u2018'ISU_CRM_PRODUCT_CHANGE'

CALL FUNCTION 'ISU_CRM_PRODUCT_CHANGE'

EXPORTING

x_vertrag = im_vertrag <<<contract for a given installation

x_keydate = im_vbeginn <<<change date

x_prodid = l_wa_crmguid-prodid

x_product = l_wa_crmguid-crm_product

x_container = container

  • X_DISPLAY_LOG =

IMPORTING

errorlog = l_log

EXCEPTIONS

NOT_FOUND = 1

ACTION_FAILED = 2

OTHERS = 3

.

When I execute the aforementioned MDT, two new records get inserted in ETTIFN table as required.

ANLAGE OPERAND AB BIS INAKTIV

5000047666 FARM 05/21/2011 12/31/9999

5000047666 SENIOR 05/11/2011 12/31/9999

However, next time when workflow sends u2018FARMu2019 as an operand value for a different date, letu2019s say 05/31/2011..then records are looking like:

ANLAGE OPERAND AB BIS INAKTIV

5000047666 FARM 05/21/2011 05/30/2011

5000047666 FARM 05/31/2011 12/31/9999

5000047666 SENIOR 05/11/2011 12/31/9999

But, ideally, before adding a new operand, if the same operand already exists, then that operand should become inactive, that is INAKTIV flag should be set (X).

ANLAGE OPERAND AB BIS INAKTIV

5000047666 FARM 05/21/2011 05/30/2011 X

5000047666 FARM 05/31/2011 12/31/9999

5000047666 SENIOR 05/11/2011 12/31/9999

Any idea on how to achieve the same?

As using MDT 'ISU_CRM_PRODUCT_CHANGEu2019 simply adds a new operand record without making an existing operand as inactive.

Former Member
Not what you were looking for? View more on this topic or Ask a question