CR is not appearing in inbox- creating ERP customer/Vendor - MDG

[former_member206605]

Hello All

Need your help...

Created MDG - Lean customer master record (7.0). I am not using BRF+ workflow for now. After submitting the CR, its not appearing in my inbox. Sharing the configuration and error log. Please let me know any setting if missing...

1. CR Type - CUSTL1 / Workflow assigned - WS54300004

2. Workflow type linkage activated

3. Assignment done - Other workflow

4. SAP_BC_BMT_WFM_SERV_USER and SAP_MDG_WF_ADM roles are assigned to WF_BATCH

5. SWU3 - Maintain Runtime environment - All green / Maintain definition env - all green / Classify tasks as general - all green. Rest 2 not required

6. Sharing the screenshot of the error -

Message was edited by: Kiran Bapat The agent table is not maintained for this workflow. I am using simple workflow. Still I need to load the agent determination table in BRF+ application? Kiran

[Former Member · Accepted solution]

Hi Kiran

Can you reconfirm below steps

Set Up the Workflow

This section describes how to make the Customizing settings required to run the workflow for the approval process in MDG-C.

You define the workflow settings in Customizing for Master Data Governance under General Settings Process Modeling Workflow.

1. Activate type linkageTo activate the type linkage, run the following activity in Customizing for Master Data Governance under General Settings Process Modeling WorkflowActivate Type Linkage . Ensure, that one object type BUS2250 has the following settings:
   • Event: CREATED
   • Receiver Type: (blank)
   • Type linkage active: yes
   • Enable event queue: deactivated
   The type linkage indicator must not be active for all other receiver types of object type BUS2250 and event CREATED. This receiver type is defined via the receiver type function module USMD_WF_RECEIVER_TYPE. NoteTo enter the receiver type function module or if you need to change the settings, mark the according line in the table and choose Goto Details.
   End of the note.
2. Configure workflow tasks.To configure workflow tasks, run the following activity in Customizing for Master Data Governance under General Settings Process Modeling WorkflowConfigure Workflow Tasks .
   1. Go to application component CA-MDG-AF and choose Assign Agents.
   2. All activities (denoted by TS*) that are not set as Background Task need to be set to General Task. To do so, select the activity, choose Attributes, and change to General Task. For MDG-C, this must be done for the Approve Change Request (TS75707980) and Revise Change Request (TS75707981) activities.
   3. Repeat the procedure for all non-background activities within the CA-MDG-APP-BP application component, at least for TS60808007 (Process Change Request), TS60808004 (Change Request Approval) and TS60807991 (MDGS Process Contact Person).
3. Check number of workflow steps
   1. To define the workflow steps for the workflows assigned to your change request types (which shall be assigned to a processor), run the following activity in Customizing for Master Data Governance under General Settings Process Modeling WorkflowOther MDG Workflows Define Workflow Step Numbers . If you use the change request types delivered with MDG-C, the following workflow steps are delivered:
      • WS54300003. Step00–03
      • WS46000023: Step00–05
      • WS46000027: Step00–04
      • WS60800095: Step00–05
   2. Assign Processors to Workflow Steps
      1. Create an organizational unit with the transaction PPOCW. Users who will process the workflow steps have to be assigned to this organizational unit.
      2. To define the workflow step numbers, run the following activity in Customizing for Master Data Governance General SettingsProcess Modeling WorkflowOther MDG Workflows Define Workflow Step Numbers
      3. To assign the object ID of the organizationoal units to the workflow step number, run the following activity in Customizing for Master Data GovernanceGeneral Settings Process Modeling WorkflowOther MDG Workflows Assign Processor to Workflow Step Number (Simple Workflow)

[former_member206605 · Accepted solution]

Thanks Sanjay

We did the same settings but still the issue was the same. After going through the entire config, I found that the workflow number given in the CR type was different than that of the workflow mention in the config document.

As per std MDG ERP customer BC set, the CR type delivered -

CUSTL1 - WS54300004 - this is the workflow assigned. Changed it to WS54300003 and its working perfectly now...

Wonder why this workflow temp is assigned to the std CT type....

Kiran

[former_member206605 · Accepted solution]

Closing the thread as the issue is resolved by changing the workflow template.

Resolution -

I found that the workflow number given in the CR type was different than that of the workflow mention in the config document.

CUSTL1 - WS54300004

CUSTL1P2 - WS54400001

( As per std MDG ERP customer BC set, the CR type delivered)'

As per the config document -

If you use the change request types delivered with MDG-C, the following workflow steps are delivered:

WS54300003. Step00–03

WS46000023: Step00–05

WS46000027: Step00–04

WS60800095: Step00–05

I changed the assignment to WS54300003 and now its working fine.

Kiran

[former_member206605]

Any suggestion on this issue?

Kiran

[former_member201266]

Hello Kiran,

No, its not required to maintain agent determination table in BRF+ for simple workflow.

For point  "3. Assignment done - other workflow" -  I hope you have configured the following:

Define Change Request Steps

Assign Processor to Change Request Step (Simple Workflow)

And can you process another record and see if any logs in SLG1.

Regards,

Sai Charan.

[former_member206605]

Thanks Sai for quick reply...

Assignment is properly done...I will process one more record and share the log..

Kiran

[former_member206605]

Hello Sai

Checked SLG1. No error. All the records processed are green.

Kiran