tc52521_AMI Standard process 2801 - negative feedback after failed AMI comm

Aim : The purpose of this test case is to verify that the AMI standard process 2801 does not generate a
BPEM in the case of a negative response from MDM in the AMI communication step, but instead reports
a negative response to 2999 so that the offline path is triggered via WFM.

US: [SBG_AG_EXT-4381] Adjustments to the 2999 AMI Standard Processes

Pre con : - Test construct according to Masterdoc IMS_Bezug_WA available - with active contract and
TaPa ID = 1000)

- Network SDoc (tab Customer, Current Time Slice) must be adjusted before the test case execution:

Gran Abre = NG (payroll granularity = no granularity)

VE.Optout = X (optout request = active)

- Argos can successfully process or complete WFM order servicing.

Data :

POD : AT0040000530200000000000002303182

Step 1 : Call the start method ZCL_IDXAT2_PROC_UTL / START_ZSPN_PROC to 8997

Step 2 : Check that process 8997 was created with the corresponding parameter from the previous step.
Step 3 : Check that step 300 - Target / actual check in process 8997 has returned a "PARTLY" result from
the TaPa class (product change possible).

Step 4 :Check that step 610 - Initiate SLA process 8999 is successful and process chain 8999-> 2999->
2801 has been started.

Step 5 : Check that process 2801 has triggered an MDUS-6 request

(CallServiceEquipmentBulkChangeRequest_Out) and that in wait step 700 is "AMI communication
response deadline".

Step 6 : Check that the process 2801 has stored the UID of the MDUS-6 service in the process header
data or that UID from the MDUS-6 request from the previous step matches the UID in the header data.

The 2801 has stored the UID of the MDUS-6 service in the process header data and this UID matches the
UID from the MDUS-6 request.
Step 7 : Simulate a negative MDUS-6 response (CallServiceEquipmentBulkChangeConfirmation_Out).

Check that the MDUC-6 confirmation message has been received in SAP.

Step 8 : Check that the wait step has been terminated in 2801 or the step "Receive event: AMI
communication - negative response" has been performed.
Step 9 : Check that the negative feedback has been returned to the chain 2999-> 8999 or the offline
process chain 8999-> 8990-> 8101 has been started.

Step 10 : Check that the process 8101 has generated a WFM request and is waiting for the WFM
response.

WFM job XML file (see u: \ slides \ smr_archive \ smr_backup) should contain the provisioning string in
the field <Measurement Product>.
Process 8101 is in step 60 - "Deadline Check: Response received from WFM".

Work Order Number is displayed in the 'Additional Header Data' tab.

Work Order Order Type is ZSSV (Service) and IHL Type is SVP (Provisioning).

Order XML contains the provisioning string in the field <Measurement Product>.
Step 11: Complete the WFM order in Argos and check that the WFM confirmation has been forwarded
to SAP. WFM confirmation was received and deadline in step 60 is scheduled.

Step 12 : Check Smartdoc and Device Data Check Update in process 8101

Step 13 : Check that SDoc network "Opt-out flagged" flag is ticked.

Step 14 : Check that the device data is updated according to OO.

Step 15 : Check that the process chain for BSL String Update 8999-> 2999-> 8091 has been created.
Step 16 : Check that an MDUS-6 request (CallServiceEquipmentBulkChangeRequest_Out) for the BSL
update has been triggered with the parameter SL and the process 8091 is in the waiting period
"Appointment for response to AMI communication".

Step 17 : Simulate a positive MDUS-6 response (CallServiceEquipmentBulkChangeConfirmation_Out).

Step 18 : Check that process 8091 has ended.

Step 19 : Check that process 8997 has been completed after steps 670 "Feedback 8999" and 850 "TAPA:
Master Data Conversion" have been carried out without error.
Step 20 : Check that the system and device are tariffed and parameterized according to the DSZ master
construct