Purchase Order storage Location Issue

Hello All,
I am trying to create a PO
The problem I am having is that the Storage location is defaulting in when I give a Plant, no matter what I do it changes back to that St location.
It is only doing that for a few material. So i am assuming its the material thats doing it
1) I check the default St location in the MRP 2 view. Made it blank
2) The material is Maintained in many st locations.
What else can cause this??
Thanks

Hi,
Check the personal settings in PO document (ME21N).
Check the Personal setting in header level.
There you can find defalut values for PO.
SAM
Edited by: Saminathan Gopalan on Jun 25, 2010 9:40 AM

Similar Messages

Storage location issue in case of BOM

Hi All,
I have a issue related to storage location determination. There are three materials X,Y and Z. Material X is main item and Y, Z are components of X. While creating sales order when we enter X it explodes BOM. Now in customizing for material X and Z storage location has been determined as SL1 but for material Y SL2 is determined. When we create delivery system automatically proposes storage location for all materials as-
Material X- SL1
Material Y- SL1
Material Z- SL1
For material X and Z it should be SL1 (which is coming right) but for Material Y it should be SL2 (but its coming as SL1 automatically)
I've checked every area right from the combination of plant, shipping point and storage condition (storage condition is different in case of Material Y). There are also no stock determination rules defined in item category and material master. SL req. and determine SL is marked for item category of each line item.
Please help me with this issue

Hi,
The system proceeds during BOM explosion to determine the issue storage locations follows:
In oppr
If you set indicator 1 Only components, the system checks to see whether the issue storage location has been maintained in the material master record of the components and uses this storage location. This storage location is then used as the withdrawal storage location and is displayed in the component list of the planned order.
If you set indicator 2 Only assembly, the system checks to see whether the proposal withdrawal location has been maintained in the production version of the assembly or finished product. If this has been maintained, the system uses this withdrawal storage location for all components and displays it in the components list in the planned order. If no proposal withdrawal location has been maintained, the system uses the assemblys receiving storage location as the withdrawal storage location for the components.
If you set indicator 3, the system first proceeds as for indicator 1 described above. If it cannot find a storage location using indicator 1, it then proceeds as described above for indicator 2.
If you set indicator 4, the system first proceeds as for indicator 2 described above. If it cannot find a storage location using indicator 2, it then proceeds as described above for indicator 1.

Mc.9 Multiple storage location issues

Hi,
I am fetching data from mc.9 in my program but if the use enter multiple storage in selection only 1st value is printed following is code and how will i come to know which material is for which storage location since mc.9 data is not getting stored anywhere
SELECT-OPTIONS : SLOC LIKE S031-LGORT.
SUBMIT RMCB0300 WITH SL_WERKS-LOW = PLNT
                    WITH SL_LGORT IN SLOC
                  WITH SL_MTART = 'HALB' WITH SL_MTART = 'VERP'
                    WITH SL_MTART = 'ROH' WITH SL_MTART = 'FERT'
                    WITH SL_SPMON-LOW = FPERIOD
                    WITH SLV_NO = 'STK'
                    WITH SL_SPMON-HIGH = FPERIOD EXPORTING LIST TO MEMORY AND RETURN.
while append to internal table even if i specify both high and low value it prints low and high incorrectly how will this problem will solved
itab-lgort = sloc-low.
Help required for same.
Thanks
Shruti

Hi Shruti,
I simulated the code given by you and all the storage locations are being populated in the backed.
You can check this by putting a breakpoint at the below code in RMCB0300 and checking the value of sl_lgort[]. You will receive the number of SLOC inputs provided.
AT SELECTION-SCREEN OUTPUT.
FLG_FOUND = FALSE.
PERFORM SPEZIAL_AT_SELECTION_SCREEN_O IN PROGRAM (LIS_PROGNAME)
                                        CHANGING FLG_FOUND
                                        IF FOUND.
This is a data issue and you may not have any records for the selected input.
Regards,
Jovito.
Edited by: dsouzajovito on Dec 29, 2010 5:56 AM

Purchase Order Outbound Idoc issue. Message Type ORDER

Hi Experts,
I am having issue with outbound IDoc generated from Purchase Order.(Message Type ORDER and Basic Type ORDERS05)
Issue is when i create PO idoc Segment E1EDP01 and field ACTION populates as 001 this works fine.
Now when made any changes to the purchase order.* PO trigers one more EDI - Idoc. but the ACTION field is stil as 002.*
Could any tell me how to fix this.
Cheers...Gopinath.

Hi,
Thank you.
I have found the issue and fixed.
Below three setting was missing same has been done in Partner Profile now ok.
Message type u2013 ORDCHG, Processing Code u2013 ME11 and Change flag On.
Cheers..Gopinath
Edited by: Gopinath A.R on Oct 8, 2009 3:14 PM

Sequencing of Purchase order and Good Issue acc. to Production order date

Hello ,
We are using Direct procurement scenario ,During MRP run we generate a Plan order(which have dates); which converted into Production order later.For these production order material is needed (components). And for procuring components we need to create purchase order.
Assumption :- Each component have same Procurement lead time
Our requirement is Purchase order and GI in Production order should be done sequentially, means Based on Production order date ,FIFO based Purchase orders are created and GI done in Production order. Production order with earlier production date have purchase orders earlier and we do GI in production order accordingly.
Kindly suggest

Hello Dario
Thanks for your reply. Our requirement is to put a check on system that GI for production order should be done FIFO wise
means as MRP generate 3 production order of same material each at different date , we want issance of components to be done on FIFO wise in production order
Regards
Rajeev

Purchase Order E- Mail Issue for Vendor .

Dear All Gurus,
User is complaining that a perticular Vendor is not getting Purchase Order throught E MAIL , i had simulated the scenario in Test Client and given an Output Type and in medium given as " 5EXTERNAL SEND ", after that i hd saved the P.O , then clicked on Print Preview but a msg appears in task bar as " E-mail address incorrect or non-existent " , Kindly help me what can i do to fix this problem I also want to know that either there is a problem in System which is responsible for sending E-mails or Vendor Email address is not OK ?
Thanx in advance ,
Rgds,
sap11

Dear,
Please check: Re: PO E-Mail Out Put Error ( E-mail address incorrect or non-existent )
Regards,
Syed Hussain.

Purchase order print out issue

hi,
we want to change the vendor address in purchase order address details, and that should printed out while taking PO. currently address is taken from vendor master. kindly assist.
regards
fozters

dear friend
this work can only be done by abap consultant.
in this po he change the address from adrc and adr6 tables
ask them to check and rectifie as specified table.
if you need the code pls keep in touch.
rewards are expecting,
yours
vivek

Purchase Order BP Name issue

Hi Experts,
The user has created Purchase Order for item in which the user has pulled vendor name from BP. But in BP the vendor name is perfect given but in Purchase Order it shows wrong vendor name. I found difficult to update purchase order. Please guide me in this.

Hi Shailesh......
The problem is coming just because user has manually typed the BP name at PO level and not taken directly from BP Master.
They should not allow to manually type BP Name as it comes directly from BP Master......
Regards,
Rahul

Purchase order generated..issue

Hi Gurus,
There is unrestricted stock for the material.But when a sles order is created for some order qty it should consume the same rite but on the other hand it had created a PR and the client says it had already been converted to PO but now the question is why the stock is not consumed.
The strategy type is blank.No reorder point or safety stock is maintained and the MRP type is PD.
Kindly revert back with your feedback
Thanks
Anand

Hi,
You have two issues .
first :- why unrestricted stock not consumed by sales order
Second :- if stock there then why it create requirement.
For first one it depends upon sales order item category i hope it require sales assign stock , u can talk with your SD consultant that he take delivery from stock so asap sales order comes it ask delivery proposal & take unrestricted stock some bit like case sale. But if your SD guy have any good reason to keep sales assign stock req then ask MM person to make 413 movement to convert stock form unrestricted to sales assign.
for point second ASAP ur sales delivry considering unrestricted stock it resolved automatically or asap 413 doc pass it resolved but if u not want this for that time also then make stratgy 10 or stratgy 40 & consumption mode & period.
Stratgy not be blank plz check OPPQ & OPPR transactions.
Thanks
Rakesh

Purchase order document overview issue

hello Experts,
My client has 6 Plants and purchase organization is central purchase organization. hence all the procurement is done from head office
following business process is followed
PR created- Release PR- RFQ with Ref to PR- PO WITH REF TO RFQ- GR - INVOICE
Problem is
1. My client does not process the PO Regularly it takes 15 to 20 days after RFQ is Selected.
2 On the other hand new PR IS generated in different plants for other material after every 2 to 3 days which is also processed and rfq is created.
My client want to see in Document Overview only those RFQ WHICH ARE NOT YET CONVERTED INTO PO. BUT WHEN I ENTER THE DETAILS THERE IS A LIST OF RFQ'S which are already processed and yet to be processed. they dont want to search rfq by date or rfq no.
if i have selected one quotation and rejected another one both of them can be seen in po document over view. and if i adopt the rejected one it gets adopted with (yellow) warning message saying the rfq is rejected and if i enter then it gets ADOPTED.
please guide me how to solve this problem
Thanks

Use the dynamic variant capability to create a variant that will only show the RFQs that are required. You can select any field in EKKO/EKPO tables for setting up this dynamic variant. Once the variant is set-up, then ask your users to make it as a default variant in me21n transaction. Now whenever ME21N is executed, this default will run in the background and will show only the relevant RFQs as the per the variant.

Incorrect Storage Location Detemined in Production Order

Hi There,
When convert planned order to Production order, storage location is determined for component material.
Till 4.7 system, we see that the system was following below sequence for determination storage location:
1)     Storage location set into BOM item
2)     Storage location determined by WC.
3)     Storage location set into material master.
However, in the upgraded ERP 6.0 system we see that the above sequence is not followed any more.
1)     Storage location determined by WC.
2)     Storage location set into material master.
3)             Storage location set into BOM item
Is our understanding correct? How can be bring back the old sequence?
Thanks in advance for your support.
Kind Regards,
Prakash

Hi Anish,
The issue is that in earlier system it was '2' as well, still the storage location was taken from BOM.
But, in ERP 6.0 it is not taken from BOM.
We do not want to change the master data for this purpose, but need a reason why SAP has changed this behaviour?
Regards,
Prakash
Edited by: Prakash Ayer on May 11, 2009 5:01 PM

Goods Issue with reference to Purchase Order

Hi MM Gurus,
Is there any settings to do Goods Issue with reference to Purchase order?
I want to capture the material price in purchase order during goods issue instead of standard price or moving average price.
Thanks in advance
Dinesh

Hello Dinesh,
Batch valuation is similar to split valuation. Here is the link on how batch valuation works.
http://help.sap.com/saphelp_47x200/helpdata/en/25/283db54f7811d18a150000e816ae6e/content.htm
Please check in sandbox environment before using.
Hope this helps.
Regards
Arif Mansuri

Purchase order message Re-determination after goods issue is posted

We have a requirement to trigger special function message type (which creates a flat file) in a purchase order when goods issue for all items are posted. We have created a requirement routine for message type to check if goods issue is posted for all line items. Goods issue is posted using BAPI which uses transaction MIGO. When goods issue is posted, we want output to be triggered in purchase order. Requirement is working fine but is there any way to trigger output automatically without going to PO?
After goods issue is posted, if we go into purchase order using ME22N then we see output proposed or if we make any changes in PO then output is proposed. This will not happen in real life though.
Any suggestion will be highly appreciated. Thanks.
Sanjay

Hello,
You can create a new output message record in NAST using RV_MESSAGE_UPDATE:
CALL FUNCTION 'RV_MESSAGE_UPDATE'
      EXPORTING
        msg_kappl = 'EF'
        msg_objky = w_objky
      TABLES
        msg_xnast = itab_nast
        msg_ynast = itab_nast_old
      EXCEPTIONS
        no_update = 1
        OTHERS    = 2.
Once the record is created, you may submit the program RSNAST00 to output the message.
Thanks,
Venu

How to get Storage Location and Vendor details in MD03 automatically

Hi folks,
We want to create automatic PR and PO from Planned Order.
But when PR gets created in MD03, the values for Purchase organization, Storage Location and fixed vendor are blank, even after maintaining source list with fixed vendor .
How to populate these values automatically ?
I am also attaching screenshot of MD03 screen

Hello
If you are creating the orders using MRP, you should make sure that the field MRP is set to 1 on the source list. The field 'fixed vendor' is not relevant to MRP. When the vendor is selected from the source list, the purchasing organization should be also copied to the purchase requisition.
The storage location will be copied from the respective field on the material master tab MRP2.
Also take a look on the following document:
MRP: Vendor is not selected and general problems on source determination
BR
Caetano

IDOC creation after the creation of a purchase order

Hi everybody,
 I want some configuration details regardign IDOC creation. The requirement is, once i create a purchase order in one system, the details should automatciaclly transfer to other system through IDOC. could any one suggest any document or detailed procedure to accomplish the task. Thanks in advance,
 Santosh.

hi santosh kumar,
Creating an IDoc Segment WE31:
The segment defines the structure of the records in an IDoc. They are defined with transaction WE31.
We will define a structure to send a text from the text database.
Transaction WE31 calls the IDoc segment editor. The editor defines the fields of a
single segment structure. The thus defined IDoc segment is then created as a data
dictionary structure. You can view the created structure with SE11 and use it in an
ABAP as any TABLES declaration.
To demonstrate the use of the IDoc segment editor we will set up an example, which
allows you to send a single text from the text pool (tables STXH and STXL) as an
IDoc. These are the texts that you can see with SO10 or edit from within many
applications.
We will show the steps to define an IDoc segment YAXX_THEAD with the DDic
structure of THEAD.
To facilitate our work, we will use the "copy-from-template-tool", which reads the
definition of a DDIC structure and inserts the field and the matching definitions as
rows in the IDoc editor. You could, of course, define the structure completely
manually, but using the template makes it easier.
The tool in release 4.0b lets you use both DDIC structures or another IDoc segment
definition as a template.
The thus created structure can be edited any time. When saving, it will create a data
dictionary structure based on the definition in WE31. The DDIC structure will retain
the same name. You can view the structure as a table definition with SE11 and use it
in an ABAP the same way.
Defining the Message Type (EDMSG)
The message type defines the context under which an IDoc is transferred to its destination. It allows for using the same IDoc file format for several different applications.
Imagine the situation of sending a purchase order to a supplier. When the IDoc with
the purchase order reaches the supplier, it will be interpreted as a sales order
received from a customer, namely you.
Simultaneously you want to send the IDoc data to the supplier's warehouse to inform
it that a purchase order has been issued and is on the way.
Both IDoc receivers will receive the same IDoc format; however, the IDoc will be
tagged with a different message type. While the IDoc to the supplier will be flagged
as a purchase order (in SAP R/3 standard: message type = ORDERS), the same IDoc
sent to the warehouse should be flagged differently, so that the warehouse can
recognize the order as a mere informational copy and process it differently than a
true purchase order.
The message type together with the IDoc type determine the processing function.
The message types are stored in table EDMSG.
Defining the message type can be done from the transaction WEDI
EDMSG: Defining the message type (1)
The entry is only a base entry which tells the system that the message type is
allowed. Other transactions will use that table as a check table to validate the entry.
IT is as shown .
EDMSG: Defining the message type (1):
The entry is only a base entry which tells the system that the message type is
allowed. Other transactions will use that table as a check table to validate the entry.
Sales Orders are being created through inbound IDocs using FM 'EDI_DATA_INCOMING'. Now a Report is required to check the status of these Inbound IDocs along with Sales Orders generated against customer Purchase Orders.
Requirement:
Sales Orders are being created through inbound IDocs using FM 'EDI_DATA_INCOMING'. Now a Report is required to check the status of these Inbound IDocs along with Sales Orders generated against customer Purchase Orders.
Processing:
The report selects, 'ORDERS' IDoc numbers & status, generated between given time range, from table EDIDC. Further, it calls Function Module 'IDOC_READ_COMPLETELY' to get the IDoc details. Then required information is extracted by reading relevant field data of IDoc segments.
sampl code:
REPORT Z_EDI_FILE_LOAD_STATUS_REPORT .
Staus Report for Inbound IDOCs ( Sales Orders )
Program : Z_EDI_FILE_LOAD_STATUS_REPORT
Presented By : www.rmtiwari.com
TABLES : EDIDC.
ALV stuff
TYPE-POOLS: SLIS.
DATA: GT_FIELDCAT TYPE SLIS_T_FIELDCAT_ALV,
 GS_LAYOUT TYPE SLIS_LAYOUT_ALV,
 GT_SORT TYPE SLIS_T_SORTINFO_ALV,
 GT_LIST_TOP_OF_PAGE TYPE SLIS_T_LISTHEADER.
DATA : BEGIN OF T_REPORT OCCURS 0,
 IDOC_NO TYPE EDI_DOCNUM,
 IDOC_DATE TYPE SY-DATUM,
 IDOC_TIME TYPE SY-UZEIT,
 SORDER_NO TYPE VBELN,
 STP_NO TYPE KNA1-KUNNR,
 STP_NAME(35) TYPE C,
 STP_PHONE(12) TYPE C,
 PO_NO(15) TYPE C,
 STATUS TYPE C,
 S_TEXT(70) TYPE C,
 ERROR(70) TYPE C,
 END OF T_REPORT.
--PARAMETER--
selection-screen begin of block date with frame title TEXT-S01.
select-options: UDATE for EDIDC-UPDDAT
 default SY-datum obligatory, "Changed On
 UTIME for EDIDC-UPDTIM . "Changed Time
selection-screen end of block date.
INITIALIZATION.
START-OF-SELECTION.
PERFORM SHOW_STATUS_REPORT.
*& Form alv_grid
 text
--> p1 text
< -- p2 text
FORM ALV_GRID.
IF GT_FIELDCAT[] IS INITIAL.
 PERFORM FIELDCAT_INIT.
 PERFORM LAYOUT_INIT.
 PERFORM SORT_INIT.
ENDIF.
PERFORM GRID_DISPLAY.
ENDFORM. "alv_grid
*& Form layout_init
FORM LAYOUT_INIT.
GS_LAYOUT-ZEBRA = 'X'.
GS_LAYOUT-CELL_MERGE = 'X'.
GS_LAYOUT-COLWIDTH_OPTIMIZE = 'X'.
GS_LAYOUT-NO_VLINE = ' '.
GS_LAYOUT-TOTALS_BEFORE_ITEMS = ' '.
ENDFORM. " layout_init
*& Form fieldcat_init
FORM FIELDCAT_INIT.
DATA: LS_FIELDCAT TYPE SLIS_FIELDCAT_ALV.
 CLEAR LS_FIELDCAT.
LS_FIELDCAT-FIELDNAME = 'IDOC_NO'.
LS_FIELDCAT-KEY = 'X'.
LS_FIELDCAT-REPTEXT_DDIC = 'IDOC'.
LS_FIELDCAT-OUTPUTLEN = 10.
Fix for ALV print bug, which puts 'N/A' over last digit
Set inttype to 'N' to stop corruption of printed ALV cell.
LS_FIELDCAT-INTTYPE = 'N'.
APPEND LS_FIELDCAT TO GT_FIELDCAT.
CLEAR LS_FIELDCAT.
LS_FIELDCAT-FIELDNAME = 'IDOC_DATE'.
LS_FIELDCAT-REPTEXT_DDIC = 'Creation Date'.
LS_FIELDCAT-OUTPUTLEN = 10.
APPEND LS_FIELDCAT TO GT_FIELDCAT.
CLEAR LS_FIELDCAT.
LS_FIELDCAT-FIELDNAME = 'IDOC_TIME'.
LS_FIELDCAT-REPTEXT_DDIC = 'Creation Time'.
LS_FIELDCAT-OUTPUTLEN = 8.
APPEND LS_FIELDCAT TO GT_FIELDCAT.
CLEAR LS_FIELDCAT.
LS_FIELDCAT-FIELDNAME = 'STATUS'.
LS_FIELDCAT-REPTEXT_DDIC = 'St'.
LS_FIELDCAT-OUTPUTLEN = 2.
APPEND LS_FIELDCAT TO GT_FIELDCAT.
CLEAR LS_FIELDCAT.
LS_FIELDCAT-FIELDNAME = 'ERROR'.
LS_FIELDCAT-REPTEXT_DDIC = 'Message'.
LS_FIELDCAT-OUTPUTLEN = 70.
APPEND LS_FIELDCAT TO GT_FIELDCAT.
CLEAR LS_FIELDCAT.
LS_FIELDCAT-FIELDNAME = 'STP_NO'.
LS_FIELDCAT-REPTEXT_DDIC = 'S.T.Party No'.
LS_FIELDCAT-OUTPUTLEN = 10.
APPEND LS_FIELDCAT TO GT_FIELDCAT.
CLEAR LS_FIELDCAT.
LS_FIELDCAT-FIELDNAME = 'STP_NAME'.
LS_FIELDCAT-REPTEXT_DDIC = 'Sold to Party Name'.
LS_FIELDCAT-OUTPUTLEN = 35.
APPEND LS_FIELDCAT TO GT_FIELDCAT.
CLEAR LS_FIELDCAT.
LS_FIELDCAT-FIELDNAME = 'PO_NO'.
LS_FIELDCAT-REPTEXT_DDIC = 'Purch Order'.
LS_FIELDCAT-OUTPUTLEN = 15.
APPEND LS_FIELDCAT TO GT_FIELDCAT.
CLEAR LS_FIELDCAT.
LS_FIELDCAT-FIELDNAME = 'STP_PHONE'.
LS_FIELDCAT-REPTEXT_DDIC = 'S.T.Party Phone'.
LS_FIELDCAT-OUTPUTLEN = 15.
APPEND LS_FIELDCAT TO GT_FIELDCAT.
ENDFORM. "fieldcat_init
*& Form sort_init
FORM SORT_INIT.
DATA: LS_SORT TYPE SLIS_SORTINFO_ALV.
CLEAR LS_SORT.
LS_SORT-FIELDNAME = 'IDOC_DATE'.
LS_SORT-SPOS = 1.
LS_SORT-UP = 'X'.
APPEND LS_SORT TO GT_SORT.
CLEAR LS_SORT.
LS_SORT-FIELDNAME = 'IDOC_TIME'.
LS_SORT-SPOS = 2.
LS_SORT-UP = 'X'.
APPEND LS_SORT TO GT_SORT.
CLEAR LS_SORT.
LS_SORT-FIELDNAME = 'STATUS'.
LS_SORT-SPOS = 3.
LS_SORT-UP = 'X'.
APPEND LS_SORT TO GT_SORT.
CLEAR LS_SORT.
LS_SORT-FIELDNAME = 'IDOC_NO'.
LS_SORT-SPOS = 4.
LS_SORT-UP = 'X'.
APPEND LS_SORT TO GT_SORT.
ENDFORM. "sort_init
*& Form grid_display
FORM GRID_DISPLAY.
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
 EXPORTING
 IS_LAYOUT = GS_LAYOUT
 IT_FIELDCAT = GT_FIELDCAT
 IT_SORT = GT_SORT
 i_callback_program = SY-REPID
 I_CALLBACK_TOP_OF_PAGE = 'TOP_OF_PAGE'
 I_DEFAULT = ' '
 I_SAVE = 'X'
 TABLES
 T_OUTTAB = T_REPORT
 EXCEPTIONS
 PROGRAM_ERROR = 1
 OTHERS = 2.
ENDFORM. "grid_display
*& Form COMMENT_BUILD
 Processing of listheader
FORM COMMENT_BUILD USING P_FK_LIST_TOP_OF_PAGE TYPE SLIS_T_LISTHEADER.
DATA: LS_LINE TYPE SLIS_LISTHEADER.
REFRESH P_FK_LIST_TOP_OF_PAGE.
List Heading : Typ H
CLEAR LS_LINE.
LS_LINE-TYP = 'H'.
LS_LINE-INFO = 'Sales Order Interface: Z_EDI_FILE_LOAD'.
APPEND LS_LINE TO P_FK_LIST_TOP_OF_PAGE.
List : Typ S
clear LS_LINE.
LS_LINE-typ = 'S'.
LS_LINE-key = 'Date Range:'.
LS_LINE-info = UDATE-low.
if not UDATE-high is initial.
 write ' To ' to LS_LINE-info+30.
 LS_LINE-info+36 = UDATE-high.
endif.
APPEND LS_LINE TO P_FK_LIST_TOP_OF_PAGE.
ENDFORM. " COMMENT_BUILD
 FORM TOP_OF_PAGE *
 Ereigniss TOP_OF_PAGE *
 event TOP_OF_PAGE
FORM TOP_OF_PAGE.
PERFORM COMMENT_BUILD USING gt_LIST_TOP_OF_PAGE[].
CALL FUNCTION 'REUSE_ALV_COMMENTARY_WRITE'
 EXPORTING
 IT_LIST_COMMENTARY = GT_LIST_TOP_OF_PAGE.
ENDFORM. "TOP_OF_PAGE
*& Form show_status_report
FORM SHOW_STATUS_REPORT .
Report to show status.
DATA: BEGIN OF T_TEDS2 OCCURS 0.
 INCLUDE STRUCTURE TEDS2.
DATA: END OF T_TEDS2.
DATA: BEGIN OF T_IDOC_CONTROL_TMP OCCURS 0.
 INCLUDE STRUCTURE EDIDC.
DATA: END OF T_IDOC_CONTROL_TMP.
CONSTANTS: C_STATUS_IN_IDOC_POSTED LIKE EDIDC-STATUS VALUE '53'.
DATA : T_EDIDS TYPE STANDARD TABLE OF EDIDS WITH HEADER LINE.
DATA : T_EDIDD TYPE STANDARD TABLE OF EDIDD WITH HEADER LINE.
DATA : GV_PARTNER_SEG TYPE E1EDKA1,
 GV_PO_REF_SEG TYPE E2EDK02.
Get text for status values
SELECT * FROM TEDS2 INTO TABLE T_TEDS2 WHERE LANGUA = SY-LANGU.
Read the IDoc's status after processing
SELECT * FROM EDIDC
 INTO TABLE T_IDOC_CONTROL_TMP
 WHERE UPDDAT IN UDATE
 AND UPDTIM IN UTIME
 AND MESTYP = 'ORDERS'.
LOOP AT T_IDOC_CONTROL_TMP.
IDoc has been processed, since control record changed.
 READ TABLE T_TEDS2 WITH KEY STATUS = T_IDOC_CONTROL_TMP-STATUS.
 T_REPORT-IDOC_NO = T_IDOC_CONTROL_TMP-DOCNUM.
 T_REPORT-IDOC_DATE = T_IDOC_CONTROL_TMP-CREDAT.
 T_REPORT-IDOC_TIME = T_IDOC_CONTROL_TMP-CRETIM.
 T_REPORT-S_TEXT = T_TEDS2-DESCRP.
 IF T_IDOC_CONTROL_TMP-STATUS = C_STATUS_IN_IDOC_POSTED.
 ok status
 T_REPORT-STATUS = 'S'.
 ELSE.
 error status
 T_REPORT-STATUS = 'E'.
 ENDIF.
 Get IDoc details.
 CALL FUNCTION 'IDOC_READ_COMPLETELY'
 EXPORTING
 DOCUMENT_NUMBER = T_REPORT-IDOC_NO
 TABLES
 INT_EDIDS = T_EDIDS
 INT_EDIDD = T_EDIDD
 EXCEPTIONS
 DOCUMENT_NOT_EXIST = 1
 DOCUMENT_NUMBER_INVALID = 2
 OTHERS = 3.
Get Error status
 READ TABLE T_EDIDS WITH KEY STATUS = T_IDOC_CONTROL_TMP-STATUS.
 IF SY-SUBRC EQ 0.
 REPLACE FIRST OCCURRENCE OF '&1' IN T_EDIDS-STATXT
 WITH T_EDIDS-STAPA1.
 REPLACE FIRST OCCURRENCE OF '&2' IN T_EDIDS-STATXT
 WITH T_EDIDS-STAPA2.
 REPLACE FIRST OCCURRENCE OF '&3' IN T_EDIDS-STATXT
 WITH T_EDIDS-STAPA3.
 REPLACE FIRST OCCURRENCE OF '&4' IN T_EDIDS-STATXT
 WITH T_EDIDS-STAPA4.
 REPLACE FIRST OCCURRENCE OF '&' IN T_EDIDS-STATXT
 WITH T_EDIDS-STAPA1.
 REPLACE FIRST OCCURRENCE OF '&' IN T_EDIDS-STATXT
 WITH T_EDIDS-STAPA2.
 REPLACE FIRST OCCURRENCE OF '&' IN T_EDIDS-STATXT
 WITH T_EDIDS-STAPA3.
 REPLACE FIRST OCCURRENCE OF '&' IN T_EDIDS-STATXT
 WITH T_EDIDS-STAPA4.
 T_REPORT-ERROR = T_EDIDS-STATXT.
 ENDIF.
 LOOP AT T_EDIDD.
 CASE T_EDIDD-SEGNAM.
 WHEN 'E1EDKA1'.
 GV_PARTNER_SEG = T_EDIDD-SDATA.
 CLEAR : T_REPORT-STP_NAME.
 CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
 EXPORTING
 INPUT = GV_PARTNER_SEG-PARTN
 IMPORTING
 OUTPUT = T_REPORT-STP_NO.
 SELECT SINGLE NAME1 TELF1
 INTO (T_REPORT-STP_NAME,T_REPORT-STP_PHONE)
 FROM KNA1
 WHERE KUNNR = T_REPORT-STP_NO.
 WHEN 'E1EDK02'.
 GV_PO_REF_SEG = T_EDIDD-SDATA.
 T_REPORT-PO_NO = GV_PO_REF_SEG-BELNR.
 ENDCASE.
 ENDLOOP.
 APPEND T_REPORT.
ENDLOOP .
SORT T_REPORT BY STATUS IDOC_NO.
Show Report
PERFORM ALV_GRID.
ENDFORM. " show_status_report
thanks
karthik
reward me points if usefull.

Purchase Order storage Location Issue

Similar Messages

Maybe you are looking for