‎2016 Jun 19 3:54 PM
Hi All,
For a z transaction creation, I have used submit statement for the report RM06EM00. While retrieving the list from memory I used the same structure of ME2M (Structure MEREP_OUTTAB_PURCHDOC).
Below is the statement I used.
SUBMIT rm06em00 WITH em_matnr IN s_matnr
WITH em_werks IN s_werks
WITH em_ekorg IN s_ekorg
WITH listu = s_listu-low
WITH selpa IN s_selpa
WITH s_bsart IN s_bsart
WITH s_ebeln IN s_ebeln
WITH s_ekgrp IN s_ekgrp
WITH s_bedat IN s_bedat
WITH s_eindt IN s_eindt
WITH s_lifnr IN s_lifnr
WITH s_matkl IN s_matkl
EXPORTING LIST TO MEMORY AND RETURN.
CALL FUNCTION 'LIST_FROM_MEMORY'
TABLES
listobject = it_list
EXCEPTIONS
not_found = 1
OTHERS = 2.
CALL FUNCTION 'LIST_TO_ASCI'
TABLES
listobject = it_list
listasci = txtlines
EXCEPTIONS
empty_list = 1
list_index_invalid = 2
OTHERS = 3.
After this I am splitting the list to corresponding fields and doing the manipulations.
This is working fine in Development system.
Below is the screen shot of structure of txtlines taken during debugging .
Development
Screenshot From Production System.
Is this structure difference is due to the layout setting or is there any configuration related to the ME2M output.
‎2016 Jun 20 6:38 AM
‎2016 Jun 19 8:10 PM
No doubt this is a "functional" question and the question would be best suited in the ERP/MM forum.
‎2016 Jun 20 6:38 AM
‎2016 Jun 23 10:21 AM
Dear Raymond,
I don't think its an issue with the scope of list. In both case I have used ALV.
The issue is not with the final Output. Issue is when using SUBMIT program and Importing the list.
when it is imported from memory its coming in different field structure. This difference is only in the production system.
Thanks & Regards,
Pradeep Alex Luke.
‎2016 Jun 23 2:40 PM
If it's ALV, then maybe there's a default ALV layout variant defined in either the dev or in the production system.
First of all, instead of testing ME2M through your program, run ME2M directly both in dev and prod system, to make sure there's the same problem than the one with your program.
If the issue comes from a default ALV layout variant, then one solution is to define the ALV layout your program is expecting, assign it as a default to a batch user, and run your SUBMIT rm06em00 in background with this batch user...