on 01-06-2016 7:05 AM
Try to put a break point on SAP side to check why your getting error message for order type PMKN.
Thanks
Manju.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Ashish,
Hi. First comment tied to your statement above is the error is via a Java return that may be tied to a backend BAPI method return that for your plant = "1109" order type PMKN has no parameters stated.
To debug this in the backend, we may need the actual BAPI Name method to run the SE 37 debugger to determine what is wrong. Hopefully your logs has this spelled out. There are hundreds and thousands (or million) of code to figure this to quickly gauge where the issue is.
Parameters could be references as input fields into your transmission. This may mean that during transmit of your transaction certain values are null or blank or empty.
If you have to compare this to the working plant during transmission what is different in the screen on your mobile devices? Is there anything that popped out? Concentrate on when you are filling out the screen during your transaction.
For example, if you have to look at any complex table available on the device is there something different for order type PMKN compared to the rest?
For example if we look at complex table with plant defined in the editor.
You have the following picture.
So in the mobile device design there are Complex table fields with certain inputs or field parameters like PriorityType or OrdType and others. If you look at your Agentry Test Environment on the downloaded Complex Table values and compare your PMKN to the other values are there any differences.
What is good is you can compare what works and what does not and see what is different.
Now another technique is to check the SAP ERP ECC backend on the definition of plants and how it differs with their column definition.
You may look at two tables in SAP:
1) T001W - Plant / Branches
and
2) T399I - Planning Plant Parameters
For item 1 and 2 above, compare your Working Order Type to the non working PMKN. It could be as simply as that the user does not have an authorization to work on the IWERK defined plant.
It could also mean that the user is a test user which is a copy from another user that does not have privilege to work on that plant.
Hope this helps out.
Best Regards,
Mark Pe
SAP Platinum Support Engineer
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
90 | |
10 | |
10 | |
10 | |
7 | |
7 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.