SAP CRM – SPROXY – test with XML variant

How to test Enterprise Services via Transaction code SPROXY.

We would like, for example, to test the functionality of sending a SalesOrder to SAP CRM, which was created via a front-end (Java) portal.

Step 1: Start transaction SPROXY
Search for the Service Interface for which you want to test and load a XML file. For example the standard SAP SalesOrderCRMCreateRequest_In.

Step 2: Double-click on the SalesOrderCRMCreateRequest_In to load the details and choose Execute (F8).

sproxy1

Step 3: In the next pop-up screen check if ‘Generate Request Template’ is selected and choose Execute (F8).

Step 4: In the following screen you will see the ‘Test Service Provider: Display Request’ with a example request.

There are different option in this step:
1. Choose an already defined variant via the variants button to directly test with already set-up test data
2. Load a XML file from your local computer.

sproxy2

Step 5: Choose Execute (F8) and you will get a success message ‘Succesful with empty result – commit may be required’

sproxy3

Step 6: Commit work is required to save the Sales Order in the database. Choose ‘Extra > Trigger COMMIT WORK’

sproxy5

Step 7: You will get a success message ‘COMMIT WORK triggered’

sproxy4

Step 8: Check for example via CRMD_ORDER the salesorder that has been created. Please note that you will have to search for the creation date/time that was put into the XML within <CreationDateTime> to find the specific order. Or use a reference ID (put in field BuyerID for example) to find the order via this value/field.

——————————————

Remco Jansen is working as a SAP CRM professional for various clients in the Netherlands.

SAP CRM – Mass reset of obsolete notes in SPAU

Symptom
After upgrade or update, in transaction SPAU, some notes may appear with grey lights. These are obsolete notes. These notes must be reset during this phase. In case there are several such notes in SPAU then it has to be performed one by one which is very time consuming and tedious task.

Other Terms
SNOTE, SPAU, Obsolete Notes, Modification Assistant

Reason and Prerequisites
Missing feature

Solution
SAP Note 1975910 consists of the feature which allows you to do this operation in bulk and in background. Mass operation to reset obsolete notes in SPAU is carried out by the job: SCWB_BGR_OBS_NOTE_RESET. Implement the relevant corrections and perform the post-manual activity to get this feature enabled on your system.

During implementation of the automatic correction instructions, the report NOTE_1975910 will be created. If you are asked for the package, please enter package SCWN. Also refer the SAP note: 1972294.

After implementation of the automatic correction instructions, the report NOTE_1975910 will be created.

– run report NOTE_1975910
– on the selection screen select Update mode <Step 2>
– when you are asked, choose activation in mode ‘Online’

——————————————

Remco Jansen is working as a SAP CRM professional for various clients in the Netherlands.