Required archive file to do purchase order processing project in oracle soa

hi,
im learning oracle soa 11g.i want to do purchase order processing project.but i cant find the pre-required archive files in net.can any one suggest where can i find this file

Hi,
Are you using Jdeveloper on a windows machine? If you are then this might be a useful tip.
Click Tools -> External Tools. It will prompt you to setup common tools. Let it do this. Now when you right click on your project you will get an Explore Directory option. I use this a lot when copying XSD’s between projects.
Once you have done this you need to click the refresh button in the Application Navigator to ensure the new files appear.
Robert

Similar Messages

Import standard Purchase Order process and interface tables

Hi all,
We are populating three PO interface tables from our custom developed application. PO_HEADERS_INTERFACE, PO_LINES_INTERFACE and PO_DISTRIBUTIONS_INTERFACE. We are using 11.5.10.2 version of Oracle Apps.
Initially we did not manage to populate the distributions interface table, but, now we are populating it. And after doing so, when we run the Import standard Purchase Order process for 'Approved' POs, the process_id for even the record which has correct distributions info also gets 'Rejected' as a value. The process is considering a mix of records : the approved POs that DO NOT HAVE distribution info in PO_DISTRIBUTIONS_INTERFACE (which we had not managed to populate) and the approved POs that HAVE distribution info in PO_DISTRIBUTIONS_INTERFACE.
does the Import standard Purchase Order process populate partial data that could be good or it rejects the whole lot of records?
Can anyone guide on this issue?
Thanks and kind regards,
Aparna
Edited by: Aparna on Jul 24, 2009 3:45 AM
Another piece of info I would like to share is
I have run the process for an approved PO with distributions info in PO_DISTRIBUTIONS_INTERFACE. This time no mixed data. In PO_INTERFACE_ERRORS table, an entry was found: for column name : PO_DISTRIBUTION_ID in ERROR_MESSAGE column 'Error: Has no distributions'.
Edited by: Aparna on Jul 24, 2009 8:03 AM
After carrying out number of tests, I have found out that
1) if the approval_status for the po is 'Approved' in the po_headers_interface table, it gives the above mentioned error and the process_id is 'rejected'.
2) if the approval_status for the po is 'Incomplete' in the po_headers_interface table, the process add the 'accepted' value for the process_id. But, the charge account number is not populated in shipments.
Edited by: Aparna on Jul 31, 2009 1:07 AM
There has been some progress on this issue. The process sees distributions data into the PO_DISTRIBUTIONS_INTERFACE table. Yet the following errors are found in the process log file:
Start dist default process
before getting period name
after getting period name
-->Intfc error occurred ...PO_PDOI_INVALID_GL_ENC_PER
before workflow
unit price = 18.5, rate = , unit price in functional currency = 18.5
after workflow
Start dist creation process
Start dist validation process
-->Intfc error occurred ...PO_PDOI_INVALID_BUDGET_ACCT
Start insert new record into po_distributions
Distribution ID: 252
dist num: 1
last updated by: 1189
po header id: 5283
po line id: 5878
line loc id: 5924
sob id: 21
cc id: 1560
qty ordered: 10
Req Header Ref num :
Req line Ref num :
Req dist id :
ROW ID: AAHUc1AFPAAAQ04AAC
call tax
Rollback for the Last Errored Line: 10
All Lines in error - Rolling back the header
We opened new GL periods for the calendar and yet same errrors are seen. Can anyone suggest any solution?
Kind regards,
Aparna

Hi
Do you have a copy of your insert statement?
regards

Outline Agreement archived before the corresponding purchase order was closed

Hi All,
I would like to know that whether an outline agreement can be archived before all the purchase orders corresponding to it are closed?
We have some open POs and the contract corresponding to that has been already archived. Please suggest,
Thanks,
Ankit

Hi Jurgen,
Thanks for the reply. I see the following for the contracts:
Contracts
The following criteria are checked if Customizing for Purchasing has been set up accordingly:
The target value has been reached (within the tolerance limits)
The target quantity has been reached (within the tolerance limits)
The validity end date has been reached
They are no longer in use.
What does it mean that 'They are no longer in use'? Does it mean that no purchase order should be open for that particular contract?
Also, in my case the POs that are open, we are not able to delete them as while making changes it tries to open the outline agreement but does not find one as it is already archived.
Thanks and Regards,
Ankit Goel
Message was edited by: Ankit Goel

Purchase order processing status

Hi
I have a doubt regarding the purchase order processing status in the PO.
Chk table EKKO field PROCSTAT.
Can anyboby tell me the status sequence of a PO.
ie: when a PO will have the corresponding status
for ex if a PO is subject to release and if is released then the status will be 05 release completed.
Likewise need to know for other status particularly interrested in knowing status 08, 04 and 01.
Reg
Raja

>01 Version in process
when Version Management is activated and it is processed once then this indicator will come
>02 Active
after po creation or if the po is on hold this will be used
>03 In release
when the po is subjected to release and Release is Possible
>04 Partially released
when PO is Partly Released itemised release
>05 Release completed
release completed and now can be processed further
>08 Rejected
when the release of po is rejected or cancelled
regards
kunal

Individual 3RD Party Purchase Order Process Bisiness logic ?

Dear sd experts
i know I.P.O ( Individual 3RD Party Purchase Order Process)
But tell me Business process why Vendor will send stock to Company ( After Loading The stock ) Again company will receive The stock ( Unloading )
Again Company will send to customer ( Loading here )
So please tell me The business logic , my doubt Vendor will send stock Directly With out Transport charges & Loading charges
it is Doing like this Profit to all ( Vendor ,customer ,& Company also)
Please tell Me the exact business logic
Thanks a lot

Hi Kaustubh
The answer lies in how the sales order is closed and invoice is printed when the GR is done.
Please check if it is possible to update the invoice with the information you want to be printed on the Export doc and Packing slip.If this can be acheived then you print the information out of the invoice without using the delivery.
Hope this helps.
Thanks

How can I add the attachment list pdf file context to purchase order ?

Dear all,
I have use services for object in ME22N to attach PDF file to purchase order,I want to know how can I add the pdf file context to purchase order when I send the purchase order to vendor.
Thanks in advance
Best regards,
Merry

hi,
attach document through Service for Object button. Service for Object button available down side of Command screen ( in your PO screen ME22N ) .
Click your Service Object button -> Create -> Create attachment
then select your window directory ( which file you need to attach) select your file Now your system shows message Service "Create attachment" is started.
Save again your PO. You can see (open) your attachment in same field ( Service for Object ) select and Create and check attachment list. You can attach as many document in your PO.

Serialized purchase orders processable in new transaction only

Hello All,
I have a program which uses BAPI_PO_RELEASE to release the blocked POs.
A job has been scheduled to execute this program.
In the job log, I get the following
Date       Time     Message text                                                                             Message class Message no. Message type
09.02.2011 01:03:59 Release effected with release code Z2                                                         ME           106          S
09.02.2011 01:03:59 Serialized purchase orders processable in new transaction only                 MEPO          130          S
09.02.2011 01:03:59 NB-Standard PO 4501932233 changed                                                          06           023          S
Though it mentions that the release is affected, the particular PO still remains blocked.
Also there is a success message, "Serialized purchase orders processable in new transaction only", can anyone help understand this message?
Regards,
Smita

Hi Xavier ,
Purchase orders :
Open and Completed only -- All PO in EKKO Table
Open Only -- Table EKPO for which Final Invoice Indicator(EREKZ) is not set
Completed Only -- Table EKPO for which Final Invoice Indicator(EREKZ) is set
Regards
Ramesh Ch

Purchase order process for utilities, rent etc

Hi,
Could anyone explain me the purchase order process for rent, consultancy services, other facility sevices, insurance etc.
Thanks and regards
Aparna

http://www.sap-img.com/materials/account-assignment.htm

Legal Requirement to include GST in Purchase Order Output Australia?

Hello,
I am currently implementing in Australia and I need to know if it is mandatory to include GST in outputs of purchase orders ?
If it is, can anyone give me a link to a document that describes that this is a legal requirement for Australia?
rgds
GAR

wouldn't it make sense to ask the people who requested it from you to give a such a document or link?
Just putting 4 words (purchase order GST australia) into Google would give a result quicker than posting the question:
http://www.customs.gov.au/webdata/resources/files/po-term-condition.pdf
https://www.anz.com/resources/0/b/0b3720804bd5b1629639fec96010cd62/Australia-Purchase-Order-TCs.pdf?MOD=AJPERES

Blanket Purchase Order - process

Hi,
Can anyone provide me, the complete procss abt Blanket purchase order i.e the complete cycle.
as well, let us know, in whihc case , they will use this blankent orders.
thanks in advance.

In SAP, Blanket Purchase Orders refer to the business process where you have a Purchase Order with a validity period (start / end date) and a limit on the item. No Goods Receipt takes place. Payment is triggered by Invoice.
Multiple invoices can be processed. Main point is that invoices must be processed within the validity period spesified in PO. The total value of invoices must also not exceed the limit spesified in PO item. The validity period is spesified on PO Header Level, while the Limit is on Item level. The creation of Purchase requisition is Optional.
Purchase Requisitions doesn't have validity period fields, although the limit can be spesified on item level. So if users create PR's then they could type the validity period simply as text in one of the long text fields.
During invoicing, if the date is outside validity period or the amount is bigger, either a Warning or Error will occur. This setting is done in customising.
Examples on where this business process can be used include: Services: example buying flowers, travel. Perticular if the receipt process is not very formalised. It is also sometimes used for utilities (water, electricity...).
Look at processes where Financial invoices (no PO) are used. To improve control, a lot of vendor invoices could be moved to Blanket Order process.
Lets look at key fields in the Purchase Order
The Overall Limit is the value that will be used to in the check during invoicing. If Commitment is switched on in Costing, the Expected value is the value of the commitment against in this case the Cost Centre. The actual will be posted during invoicing.
Account assignment is mandatory, so this process is non stock purposes only. Stock can not be procured using this method (For stock a GR is required).
Because no Goods Receipt (GR) will take place, the GR indicator is switched off when the item category is selected
Read the Rules Use the Search...........

Planning file entry and purchase orders

Hi all:
The documentation for MRP planning states that the planning file entry is updated for relevant changes to the material that includes among other things creation of purchase orders for the material.
In our system, MRP requisition creation does update table MDVM as part of the MRP run. However, purchase order creation does not update the planning file entry, even though the documentation says it should.
Anyone ever encounter this? Are there controls that need to be set?
thanks in advance
weston

Not sure where you had read that a Purchase order creation updates the PFE. Have a look at this.
http://forums.sdn.sap.com/thread.jspa?threadID=2129091&messageID=11046363#11046363
Edited by: UKSAPPP on Feb 16, 2012 6:27 AM

Archiving PO older MM_EKKO (purchase order)

Hello,
I need archiving PO older (more than 10 years old), but this PO when execute preprocessing program RM06EV47 and most of them can not be marked for deletion, for many reasons. Eg. e06(115) "Quantity delivered differs from qty. invoiced (Function not possible)" and other messages
I already tested with
Program: RWPOB001 (Transaction WPO1)
BADI: ARC_MM_EKKO_CHECK
But I can not mark it for deletion (prerequisite for archivign PO).
Is there a standard way to close that inconistentes Purchase order ?
I want to avoid
UPDATE EKKO-LOEKZ = 'L'.
Thanks
Edited by: Cervantes Nicolas on Oct 4, 2010 5:58 PM

Cervantes Nicolas wrote:
I need archiving PO older (more than 10 years old), but this PO when execute preprocessing program RM06EV47 and most of them can not be marked for deletion, for many reasons. Eg. e06(115) "Quantity delivered differs from qty. invoiced (Function not possible)" and other messages
If your PO shows E06(115), use transaction MASS, BUS2012 to flag both: EKPO-ELIKZ ("Delivery Completed" Indicator) and EKPO-EREKZ (Final invoice indicator). This should let the PO pass - I was in the same situation and finally managed to get rid of 98% of inconsistent PO's.
In addition: search in OSS for notes on the subject, especially with keyword RM06EV47 - there are a couple of notes explaining what to do to pass the prepare-run.

Upload of excel file in to purchase order

hi guys,
              i want to upload a excel file to the internal table and then to create the purchase order.
i know the name of function module and bapi.
but how to make use of them in implementation!!!
fun module : ALSM_EXCEL_TO_INTERNAL_TABLE
bapi :       BAPI_PO_CREATE1.
                                                                                arun and vishnu from
                                                                infotech solutions

*CREATION OF A TEMPORARY STRUCTURE FOR INSERTING FIELDS OF EXCEL TO INTERNAL TABLE.
TYPES : BEGIN OF STR_FINAL,
         COMP_CODE TYPE BAPIMEPOHEADER-COMP_CODE,    " STRUCTURE : BAPIMEPOHEADER
         ITEM_INTVL TYPE BAPIMEPOHEADER-ITEM_INTVL,
         VENDOR TYPE BAPIMEPOHEADER-VENDOR,
         PMNTTRMS TYPE BAPIMEPOHEADER-PMNTTRMS,
         PURCH_ORG TYPE BAPIMEPOHEADER-PURCH_ORG,
         PUR_GROUP TYPE BAPIMEPOHEADER-PUR_GROUP,
         CURRENCY TYPE BAPIMEPOHEADER-CURRENCY,
         PO_ITEM TYPE BAPIMEPOITEM-PO_ITEM,         " STRUCTURE : BAPIMEPOITEM
         MATERIAL TYPE BAPIMEPOITEM-MATERIAL,
         PLANT TYPE BAPIMEPOITEM-PLANT,
         STGE_LOC TYPE BAPIMEPOITEM-STGE_LOC,
         QUANTITY TYPE BAPIMEPOITEM-QUANTITY,
         TAX_CODE TYPE BAPIMEPOITEM-TAX_CODE,
         ITEM_CAT TYPE BAPIMEPOITEM-ITEM_CAT,
         ACCTASSCAT TYPE BAPIMEPOITEM-ACCTASSCAT,
         SCHED_LINE TYPE BAPIMEPOSCHEDULE-SCHED_LINE,        " STRUCTURE : BAPIMEPOSCHEDULE
         DELIVERY_DATE TYPE BAPIMEPOSCHEDULE-DELIVERY_DATE,
         SERIAL_NO TYPE BAPIMEPOACCOUNT-SERIAL_NO,           " STRUCTURE : BAPIMEPOACCOUNT
         GL_ACCOUNT TYPE BAPIMEPOACCOUNT-GL_ACCOUNT,
         COSTCENTER TYPE BAPIMEPOACCOUNT-COSTCENTER,
         CO_AREA TYPE BAPIMEPOACCOUNT-CO_AREA,
         END OF STR_FINAL.
DATA :   IT_FINAL TYPE TABLE OF STR_FINAL,
         WA_FINAL TYPE STR_FINAL.
DATA: ST_BAPIMEPOHEADER TYPE BAPIMEPOHEADER,
      ST_BAPIMEPOHEADERX TYPE BAPIMEPOHEADERX.
*it is for item data
DATA: WA_POITEM TYPE BAPIMEPOITEM,
      IT_POITEM TYPE TABLE OF BAPIMEPOITEM,
      WA_POITEMX TYPE BAPIMEPOITEMX,
      IT_POITEMX TYPE TABLE OF BAPIMEPOITEMX,
      WA_POSCHEDULE TYPE BAPIMEPOSCHEDULE,
      IT_POSCHEDULE TYPE TABLE OF BAPIMEPOSCHEDULE,
      WA_POSCHEDULEX TYPE BAPIMEPOSCHEDULX,
      IT_POSCHEDULEX TYPE TABLE OF BAPIMEPOSCHEDULX,
      WA_POACCOUNT TYPE BAPIMEPOACCOUNT,
      IT_POACCOUNT TYPE TABLE OF BAPIMEPOACCOUNT,
      WA_POACCOUNTX TYPE BAPIMEPOACCOUNTX,
      IT_POACCOUNTX TYPE TABLE OF BAPIMEPOACCOUNTX,
      WA_RETURN TYPE BAPIRET2,
      IT_RETURN TYPE TABLE OF BAPIRET2.
selection-screen skip 1.
parameters: p_file type localfile default 'D:\VISHNU\DEMO.XLS'.
*selection-screen skip 1.
at selection-screen on value-request for p_file.
call function 'KD_GET_FILENAME_ON_F4'
       exporting
            static    = 'X'
       changing
            file_name = p_file.
start-of-selection.
clear IT_FINAL.
refresh IT_FINAL.
perform upload_data.
loop at IT_FINAL INTO WA_FINAL.
    write:/ WA_FINAL-COMP_CODE,
          / WA_FINAL-ITEM_INTVL,
          / WA_FINAL-VENDOR,
          / WA_FINAL-PMNTTRMS,
          / WA_FINAL-PURCH_ORG,
          / WA_FINAL-PUR_GROUP,
          / WA_FINAL-CURRENCY,
          / WA_FINAL-PO_ITEM,
          / WA_FINAL-MATERIAL,
          / WA_FINAL-PLANT,
          / WA_FINAL-STGE_LOC,
          / WA_FINAL-QUANTITY,
          / WA_FINAL-TAX_CODE,
          / WA_FINAL-ITEM_CAT,
          / WA_FINAL-ACCTASSCAT,
          / WA_FINAL-SCHED_LINE,
          / WA_FINAL-DELIVERY_DATE,
          / WA_FINAL-SERIAL_NO,
          / WA_FINAL-GL_ACCOUNT,
          / WA_FINAL-COSTCENTER,
          / WA_FINAL-CO_AREA.
endloop.
LOOP AT IT_FINAL INTO WA_FINAL.
ST_BAPIMEPOHEADER-COMP_CODE = WA_FINAL-COMP_CODE.
ST_BAPIMEPOHEADER-DOC_TYPE = 'NB'.
ST_BAPIMEPOHEADER-ITEM_INTVL = WA_FINAL-ITEM_INTVL.
ST_BAPIMEPOHEADER-VENDOR = WA_FINAL-VENDOR.
ST_BAPIMEPOHEADER-LANGU = SY-LANGU.
ST_BAPIMEPOHEADER-PMNTTRMS = WA_FINAL-PMNTTRMS.
ST_BAPIMEPOHEADER-PURCH_ORG = WA_FINAL-PURCH_ORG.
ST_BAPIMEPOHEADER-PUR_GROUP = WA_FINAL-PUR_GROUP.
ST_BAPIMEPOHEADER-CURRENCY = WA_FINAL-CURRENCY.
*insert ST_BAPIMEPOHEADERX values
ST_BAPIMEPOHEADERX-COMP_CODE = 'X'.
ST_BAPIMEPOHEADERX-DOC_TYPE = 'X'.
ST_BAPIMEPOHEADERX-ITEM_INTVL = 'X'.
ST_BAPIMEPOHEADERX-VENDOR = 'X'.
ST_BAPIMEPOHEADERX-LANGU = 'X'.
ST_BAPIMEPOHEADERX-PMNTTRMS = 'X'.
ST_BAPIMEPOHEADERX-PURCH_ORG = 'X'.
ST_BAPIMEPOHEADERX-PUR_GROUP = 'X'.
ST_BAPIMEPOHEADERX-CURRENCY = 'X'.
*insert IT_POITEM values
WA_POITEM-PO_ITEM = WA_FINAL-PO_ITEM.
WA_POITEM-MATERIAL = WA_FINAL-MATERIAL.
WA_POITEM-PLANT = WA_FINAL-PLANT.
WA_POITEM-STGE_LOC = WA_FINAL-STGE_LOC.
WA_POITEM-QUANTITY = WA_FINAL-QUANTITY.
WA_POITEM-TAX_CODE = WA_FINAL-TAX_CODE.
WA_POITEM-ITEM_CAT = WA_FINAL-ITEM_CAT.
WA_POITEM-ACCTASSCAT = WA_FINAL-ACCTASSCAT.
APPEND WA_POITEM TO IT_POITEM.
CLEAR WA_POITEM.
*insert IT_POITEMX values
WA_POITEMX-PO_ITEM = WA_FINAL-PO_ITEM.
WA_POITEMX-PO_ITEMX = 'X'.
WA_POITEMX-MATERIAL = 'X'.
WA_POITEMX-PLANT = 'X'.
WA_POITEMX-STGE_LOC = 'X'.
WA_POITEMX-QUANTITY = 'X'.
WA_POITEMX-TAX_CODE = 'X'.
WA_POITEMX-ITEM_CAT = 'X'.
WA_POITEMX-ACCTASSCAT = 'X'.
APPEND WA_POITEMX TO IT_POITEMX.
CLEAR WA_POITEMX.
*insert IT_POSCHEDULE values
WA_POSCHEDULE-PO_ITEM = WA_FINAL-PO_ITEM.
WA_POSCHEDULE-SCHED_LINE = WA_FINAL-SCHED_LINE.
WA_POSCHEDULE-DELIVERY_DATE = WA_FINAL-DELIVERY_DATE .
WA_POSCHEDULE-QUANTITY = WA_FINAL-QUANTITY.
APPEND WA_POSCHEDULE TO IT_POSCHEDULE.
CLEAR WA_POSCHEDULE.
*insert IT_POSCHEDULEX values
WA_POSCHEDULEX-PO_ITEM = WA_FINAL-PO_ITEM.
WA_POSCHEDULEX-SCHED_LINE = WA_FINAL-SCHED_LINE.
WA_POSCHEDULEX-PO_ITEMX = 'X' .
WA_POSCHEDULEX-SCHED_LINEX = 'X' .
WA_POSCHEDULEX-DELIVERY_DATE = 'X' .
WA_POSCHEDULEX-QUANTITY = 'X' .
WA_POSCHEDULEX-PO_ITEM = WA_FINAL-PO_ITEM .
WA_POSCHEDULEX-SCHED_LINE = WA_FINAL-SCHED_LINE.
WA_POSCHEDULEX-PO_ITEMX = 'X'.
WA_POSCHEDULEX-SCHED_LINEX = 'X' .
WA_POSCHEDULEX-DELIVERY_DATE = 'X' .
WA_POSCHEDULEX-QUANTITY = 'X'.
WA_POSCHEDULEX-PO_ITEM = WA_FINAL-PO_ITEM.
WA_POSCHEDULEX-SCHED_LINE = WA_FINAL-SCHED_LINE.
WA_POSCHEDULEX-PO_ITEMX = 'X'.
WA_POSCHEDULEX-SCHED_LINEX = 'X'.
WA_POSCHEDULEX-DELIVERY_DATE = 'X' .
WA_POSCHEDULEX-QUANTITY = 'X'.
APPEND WA_POSCHEDULEX TO IT_POSCHEDULEX.
CLEAR WA_POSCHEDULEX.
*insert IT_POACCOUNT values
WA_POACCOUNT-PO_ITEM = WA_FINAL-PO_ITEM.
WA_POACCOUNT-SERIAL_NO = WA_FINAL-SERIAL_NO.
WA_POACCOUNT-QUANTITY = WA_FINAL-QUANTITY .
WA_POACCOUNT-GL_ACCOUNT = WA_FINAL-GL_ACCOUNT.
WA_POACCOUNT-COSTCENTER = WA_FINAL-COSTCENTER.
WA_POACCOUNT-CO_AREA = WA_FINAL-CO_AREA.
APPEND WA_POACCOUNT TO IT_POACCOUNT.
CLEAR WA_POACCOUNT.
*insert IT_POACCOUNTX values
WA_POACCOUNTX-PO_ITEM = 00001.
WA_POACCOUNTX-SERIAL_NO = 01.
WA_POACCOUNTX-QUANTITY = 'X'.
WA_POACCOUNTX-GL_ACCOUNT = 'X'.
WA_POACCOUNTX-COSTCENTER = 'X' .
WA_POACCOUNTX-CO_AREA = 'X'.
APPEND WA_POACCOUNTX TO IT_POACCOUNTX.
CLEAR WA_POACCOUNTX.
ENDLOOP.
CALL FUNCTION 'BAPI_PO_CREATE1'
EXPORTING
    POHEADER                     = ST_BAPIMEPOHEADER
   POHEADERX                     = ST_BAPIMEPOHEADERX
POADDRVENDOR                 =
TESTRUN                      =
MEMORY_UNCOMPLETE            =
MEMORY_COMPLETE              =
POEXPIMPHEADER               =
POEXPIMPHEADERX              =
VERSIONS                     =
IMPORTING
EXPPURCHASEORDER             =
EXPHEADER                    =
EXPPOEXPIMPHEADER            =
TABLES
   RETURN                       = IT_RETURN
   POITEM                       = IT_POITEM
   POITEMX                      = IT_POITEMX
POADDRDELIVERY               =
   POSCHEDULE                   = IT_POSCHEDULE
   POSCHEDULEX                  = IT_POSCHEDULEX
   POACCOUNT                    = IT_POACCOUNT
POACCOUNTPROFITSEGMENT       =
   POACCOUNTX                   = IT_POACCOUNTX
POCONDHEADER                 =
POCONDHEADERX                =
POCOND                       =
POCONDX                      =
POLIMITS                     =
POCONTRACTLIMITS             =
POSERVICES                   =
POSRVACCESSVALUES            =
POSERVICESTEXT               =
EXTENSIONIN                  =
EXTENSIONOUT                 =
POEXPIMPITEM                 =
POEXPIMPITEMX                =
POTEXTHEADER                 =
POTEXTITEM                   =
ALLVERSIONS                  =
POPARTNER                    =
*this is for save the porder number
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'.
*dispaly the results
LOOP AT IT_RETURN INTO WA_RETURN.
WRITE:/ WA_RETURN-MESSAGE,
          ST_BAPIMEPOHEADER-PO_NUMBER.
ENDLOOP.
form upload_data.
data: file type rlgrap-filename.
data: IT_XCEL type table of alsmex_tabline,
        WA_XCEL TYPE ALSMEX_TABLINE.
file = p_file.
call function 'ALSM_EXCEL_TO_INTERNAL_TABLE'
       exporting
            filename                = file
            i_begin_col             = '1'
            i_begin_row             = '1'
            i_end_col               = '21'
            i_end_row               = '1'
       tables
            intern                  = IT_xcel
       exceptions
            inconsistent_parameters = 1
            upload_ole              = 2
            others                  = 3.
loop at IT_xcel INTO WA_XCEL.
    case
        WA_XCEL-COL.
        when '0001'.
        WA_FINAL-COMP_CODE = WA_xcel-value.
        WHEN '0002'.
        WA_FINAL-ITEM_INTVL = WA_XCEL-VALUE.
        WHEN '0003'.
        WA_FINAL-VENDOR = WA_XCEL-VALUE.
        WHEN '0004'.
        WA_FINAL-PMNTTRMS = WA_XCEL-VALUE.
        WHEN '0005'.
        WA_FINAL-PURCH_ORG = WA_XCEL-VALUE.
        WHEN '0006'.
        WA_FINAL-PUR_GROUP = WA_XCEL-VALUE.
        WHEN '0007'.
        WA_FINAL-CURRENCY = WA_XCEL-VALUE.
        WHEN '0008'.
        WA_FINAL-PO_ITEM = WA_XCEL-VALUE.
        WHEN '0009'.
        WA_FINAL-MATERIAL = WA_XCEL-VALUE.
        WHEN '00010'.
        WA_FINAL-PLANT = WA_XCEL-VALUE.
        WHEN '00011'.
        WA_FINAL-STGE_LOC = WA_XCEL-VALUE.
        WHEN '00012'.
        WA_FINAL-QUANTITY = WA_XCEL-VALUE.
        WHEN '00013'.
        WA_FINAL-TAX_CODE = WA_XCEL-VALUE.
        WHEN '00014'.
        WA_FINAL-ITEM_CAT = WA_XCEL-VALUE.
        WHEN '00015'.
        WA_FINAL-ACCTASSCAT = WA_XCEL-VALUE.
        WHEN '00016'.
        WA_FINAL-SCHED_LINE = WA_XCEL-VALUE.
        WHEN '00017'.
        WA_FINAL-DELIVERY_DATE = WA_XCEL-VALUE.
        WHEN '00018'.
        WA_FINAL-SERIAL_NO = WA_XCEL-VALUE.
        WHEN '00019'.
        WA_FINAL-GL_ACCOUNT = WA_XCEL-VALUE.
        WHEN '00020'.
        WA_FINAL-COSTCENTER = WA_XCEL-VALUE.
        WHEN '00021'.
        WA_FINAL-CO_AREA = WA_XCEL-VALUE.
        ENDCASE.
        at end of row.
      append WA_FINAL TO IT_FINAL.
     clear WA_FINAL.
    endat.
ENDLOOP.
ENDFORM.

Third party Purchase order processing

Dear Experts,
In one of our business scenario we are purchasing materials from vendor and directly supplied it to customer,physical goods receipt is not done at our location,for third party account assignment in mandatory.
I have given account assignment as sales order ( C ) and in item category I have mention(THIRD PARTY- S ).
When I go for Invoice posting I am getting error ie.Enter GL Account
Please advice how to resolve this issue.Also mention what setting are needed for Third party order processing against account assignment as sales order.
Thanks

Hi
If you are doing third party order processing,
While creating the Sales order, it will create a purchase requisition in the back end. ( For thid in sales order line item, item category should be TAS)
While converting the PR to PO( all the account assingment would be copied).
Check the line tem of PR or PO - Account assignment Tab - G/L account and Sales order no).
I beleive it will automatically pick the sales order no and account assignment( G/L account) for the line item while creating PR.
Check it out.
Regards,
Raman

U00A7ECH Engineering Change with Purchase Order, Process Order and Sales Order

Hello All,
Can someone kindly explain me the integration points of Engineering Change with
1. Purchase Order
2. Process Order
3. Sales Order
I know we can see the Rev Letter in the first two. Is there a 'refresh' function inside the PO, Process Order, Sales Order by which we can get the latest and greatest revision, incase the material rev is updated/changed after the PO, Proc Order, SO is already created. Also if yes,after what status in PO, Process Order or Sales Order we cannot use the 'Refresh' button, and than what needs to be done to fix this situation.
Thanks in advance,
Sachin

Hi,
really, this depends on several factors, especially the valid from date of the ECM and its impact on changes on a BOM (which I suppose is the use case you are looking at? Or just a change on the material revision of the BOM header material?
Interesting for you should also be Order Change Management, although not applicable to process orders as far as I know:
[http://help.sap.com/saphelp_erp60_sp/helpdata/en/41/3699761bc211d2b62b0000e8359890/frameset.htm]
Regards, Ulf.

Required archive file to do purchase order processing project in oracle soa

Similar Messages

Maybe you are looking for