EDI output for PO cancellation

Hi Gurus,
can anybody please throw some light on why the IDOC is not generated for a PO cancellation. When i save the PO after cancelling the line, the output on the messages tab fails with a red message saying that "no items exist" and there is no idoc. then how will we communicate to our vendor that we have cancelled the PO? please share some thoughts
Thanks
Anusha

Hi Jurgen,
Found it. all that we had to was to create another partner profile for ORDCHG and then have the change flag for ORDCHG and keep the ORDR without the flag on the message control in WE20. By doing this now we are able to send the changes and cancellatrions with ORDCHG and the newly created PO with ORDR message type.
Thank you so much for your help.
Anusha
Edited by: anusha vemulapati on Aug 4, 2011 11:56 PM

Similar Messages

EDI Output for Material Document(Application ME)

Does anybody have the experience of having set up an EDI putput for a Mmaterial Document( Application "ME")?
I tried to configure a new output type by assigning it with Program RSNASTED and routine EDI_PROCESSING.
Setting up the partner profile is still pending but when i created a test document by creating a condition record i get an error message "Purchasing document XXXXX does not exist" where XXXXX happens to be the Material document number in this case.
Before proceeding further i just want to ensure if i am using the correct programs and Routines and i havent seen any available EDI output type provided by SAP for application ME.
Appreciate your response and inputs to proceed further.
Suman

Does anybody have the experience of having set up an EDI putput for a Mmaterial Document( Application "ME")?
I tried to configure a new output type by assigning it with Program RSNASTED and routine EDI_PROCESSING.
Setting up the partner profile is still pending but when i created a test document by creating a condition record i get an error message "Purchasing document XXXXX does not exist" where XXXXX happens to be the Material document number in this case.
Before proceeding further i just want to ensure if i am using the correct programs and Routines and i havent seen any available EDI output type provided by SAP for application ME.
Appreciate your response and inputs to proceed further.
Suman

Debugging EDI output (IDOC creation) for purchase order...

Hi,
We have a EDI output type defined for Purchase order. When I go to Messages tab in ME22N transaction and repeat the EDI output and save it, it creates a IDOC which I can see using transaction WE02.
Now the problem is there is a user exit which I know gets triggered, when the IDOC is created for this PO. When we do some changes in this user exit, I see those changes are reflected when new IDOC is created. But if I put breakpoint, and do repeat output -> save, the debugger does not stop there.
Is there is some technique I can see the breakpoint stoppage in user exit for IDOC creation during EDI output for Purchase order ?
Regards,
Rajesh

Hi
Youc can set the output Peridoically (After Giving the output type, set the furthere data as periodic).
Save.
Set the break point in your user exit.
Go to se 38 -> Run RSNAST00,
Give the object id (Your PO #)
Give the output type and execute, the control will stop at break point.
Regards,
Baburaj

Output for EDI

hiall,
here i have a scenario where i have to give Advance shipment Notification to the customer ,now i have made the basic setting of EDI and the output cond type i'm using is LAVA.which is in the delivery.
now when i do issue output i could see the green traffic signal assigned the o/p type Lava but could not see the output.
is there is any way that i can see the EDI output?
so that i can take a printout of that.
thanks
vijay

hi
thanks for the reply,in we05,we02 i could see the idoc generated ,but in that i could not see the delivery date i.e the date when the goods will reach the customer.
with this date i could intimate the customer that the goods will reach them in so and so date.
pls do tell me where can i see the delivery date form the idoc.
thanks
vijay

EDI output triggered for old PO

Hello All,
on 09.09.2014, EDI ( output type NEU, transmission medium 6) output type has triggered for more than 700 PO's which has been created in 2012 for several vendors and sent to supplier again as a duplicate copy. Suppliers are reaching client for this and some suppliers started sending goods which client has not ordered. There are no changes available in PO and users have not edited those PO's. There is no batch job scheduled to trigger output type. How else is possible for triggering output type in old PO. Please share your ideas.
Regards,
Prasath J

Ask your basis team when the last copy was done. if the copy was done between creation date and now, then the PO in the copy system will show how the PO was before the incident happened.
This way you can see if there were unprocessed messages.
Message records do not create by itself in old POs, And 700 cases do not speak for a manual activity either,especially as you are saying that you have no change records.
Maybe there was something done programatically to solve an earlier problem from you:
PO Output Message Disappears

Output type and application for order cancellation

What is the output type and application for the cancellation of a sales order

Hi,
Try This
cancellation of sales order:
go to va02 enter the sales order and click enter
then sales document->delete
Reward if usefull

CANCEL_FLAG in PO Output for Communication

I'm trying to build logic into an RTF template for the "PO Output for Communication" report to handle cancelled lines. The cancel_flag can be set to "Y" at any of 3 levels - PO Header, PO Line and PO shipment. The field is called the same thing (cancel_flag) at all 3 levels.
In my rtf template, I have a row in a table to display each PO line using the for-each clause. I do not want to display lines which are cancelled (ie where CANCEL_FLAG (at line level) = 'Y'.
How do I reference the CANCEL_FLAG specifally at line level (not header, and shipment line)??
My xml is as follows:
<?xml version="1.0" encoding="UTF-8"?>
<PO_DATA>
<TYPE_LOOKUP_CODE>STANDARD</TYPE_LOOKUP_CODE>
<SEGMENT1>33832</SEGMENT1>
<REVISION_NUM>0</REVISION_NUM>
<PRINT_COUNT>0</PRINT_COUNT>
<CREATION_DATE>10-DEC-2009 17:42:27</CREATION_DATE>
<DOCUMENT_BUYER_FIRST_NAME>Happiness</DOCUMENT_BUYER_FIRST_NAME>
<DOCUMENT_BUYER_LAST_NAME>Makeleni</DOCUMENT_BUYER_LAST_NAME>
<DOCUMENT_BUYER_TITLE>MS.</DOCUMENT_BUYER_TITLE>
<DOCUMENT_BUYER_AGENT_ID>4588</DOCUMENT_BUYER_AGENT_ID>
<CONFIRMING_ORDER_FLAG>N</CONFIRMING_ORDER_FLAG>
<ACCEPTANCE_REQUIRED_FLAG>N</ACCEPTANCE_REQUIRED_FLAG>
<CURRENCY_CODE>ZAR</CURRENCY_CODE>
<CURRENCY_NAME>Rand</CURRENCY_NAME>
<PAYMENT_TERMS>30 Days 2.5% Discount</PAYMENT_TERMS>
<VENDOR_NUM>LAP005</VENDOR_NUM>
<VENDOR_NAME>LAPACK (PTY) LTD</VENDOR_NAME>
<VENDOR_ADDRESS_LINE1>P O Box 1082</VENDOR_ADDRESS_LINE1>
<VENDOR_CITY>Isando</VENDOR_CITY>
<VENDOR_STATE>RSA</VENDOR_STATE>
<VENDOR_POSTAL_CODE>1600</VENDOR_POSTAL_CODE>
<VENDOR_COUNTRY>South Africa</VENDOR_COUNTRY>
<VENDOR_PHONE>9741531</VENDOR_PHONE>
<SHIP_TO_LOCATION_ID>71695</SHIP_TO_LOCATION_ID>
<SHIP_TO_LOCATION_NAME>23M CS Isando Personal Care</SHIP_TO_LOCATION_NAME>
<SHIP_TO_ADDRESS_LINE1>23M CS Isando Personal</SHIP_TO_ADDRESS_LINE1>
<SHIP_TO_ADDRESS_LINE2>22 Purlin Road</SHIP_TO_ADDRESS_LINE2>
<SHIP_TO_ADDRESS_INFO>Isando, GP 1600</SHIP_TO_ADDRESS_INFO>
<SHIP_TO_COUNTRY>South Africa</SHIP_TO_COUNTRY>
<BILL_TO_LOCATION_ID>78573</BILL_TO_LOCATION_ID>
<BILL_TO_LOCATION_NAME>Tiger Brands Consumer Manufacturing</BILL_TO_LOCATION_NAME>
<BILL_TO_ADDRESS_LINE1>P O Box 527</BILL_TO_ADDRESS_LINE1>
<BILL_TO_ADDRESS_INFO>Paarl, 7620</BILL_TO_ADDRESS_INFO>
<BILL_TO_COUNTRY>South Africa</BILL_TO_COUNTRY>
<VENDOR_SITE_ID>95462</VENDOR_SITE_ID>
<PO_HEADER_ID>711318</PO_HEADER_ID>
<APPROVED_FLAG>N</APPROVED_FLAG>
<VENDOR_ID>73269</VENDOR_ID>
<CLOSED_CODE>OPEN</CLOSED_CODE>
<ORG_ID>1296</ORG_ID>
<FIRM_STATUS_LOOKUP_CODE>N</FIRM_STATUS_LOOKUP_CODE>
<FROZEN_FLAG>N</FROZEN_FLAG>
<CREATED_BY>7794</CREATED_BY>
<TERMS_ID>10006</TERMS_ID>
<RATE_DATE>10-DEC-2009 00:00:00</RATE_DATE>
<AUTHORIZATION_STATUS>N</AUTHORIZATION_STATUS>
<LAST_UPDATE_DATE>10-DEC-2009 17:50:02</LAST_UPDATE_DATE>
<LAST_UPDATED_BY>7794</LAST_UPDATED_BY>
<SUMMARY_FLAG>N</SUMMARY_FLAG>
<ENABLED_FLAG>Y</ENABLED_FLAG>
<LAST_UPDATE_LOGIN>52339081</LAST_UPDATE_LOGIN>
<CONTERMS_EXIST_FLAG>N</CONTERMS_EXIST_FLAG>
<PENDING_SIGNATURE_FLAG>N</PENDING_SIGNATURE_FLAG>
<OU_NAME>CS Consumer National (A90)</OU_NAME>
<OU_ADDR1>Corporate Hill Office Park</OU_ADDR1>
<OU_ADDR2>William Nicholl Drive</OU_ADDR2>
<OU_TOWN_CITY>Bryanston</OU_TOWN_CITY>
<OU_REGION2>GP</OU_REGION2>
<OU_POSTALCODE>1768</OU_POSTALCODE>
<OU_COUNTRY>South Africa</OU_COUNTRY>
<BUYER_LOCATION_ID>71695</BUYER_LOCATION_ID>
<BUYER_ADDRESS_LINE1>23M CS Isando Personal</BUYER_ADDRESS_LINE1>
<BUYER_ADDRESS_LINE2>22 Purlin Road</BUYER_ADDRESS_LINE2>
<BUYER_CITY_STATE_ZIP>Isando, GP 1600</BUYER_CITY_STATE_ZIP>
<BUYER_CONTACT_EMAIL>[email protected]</BUYER_CONTACT_EMAIL>
<VENDOR_FAX>3925820</VENDOR_FAX>
<TOTAL_AMOUNT>246,321.92</TOTAL_AMOUNT>
<BUYER_COUNTRY>South Africa</BUYER_COUNTRY>
<VENDOR_AREA_CODE>011</VENDOR_AREA_CODE>
<LE_NAME>AI Health Care (Pty) LTD</LE_NAME>
<LE_ADDR1>Coprporate Hill Office Park</LE_ADDR1>
<LE_ADDR2>Willima Nicholl Drive</LE_ADDR2>
<LE_TOWN_CITY>Bryanston</LE_TOWN_CITY>
<LE_STAE_PROVINCE>GP</LE_STAE_PROVINCE>
<LE_POSTALCODE>1768</LE_POSTALCODE>
<LE_COUNTRY>South Africa</LE_COUNTRY>
<DOCUMENT_CREATION_METHOD>AUTOCREATE</DOCUMENT_CREATION_METHOD>
<DOCUMENT_TYPE>Standard Purchase Order</DOCUMENT_TYPE>
<TEST_FLAG>D</TEST_FLAG>
<DIST_SHIPMENT_COUNT>1</DIST_SHIPMENT_COUNT>
<DOCUMENT_NAME>Standard Purchase Order 33832, 0</DOCUMENT_NAME>
<SIGNED>F</SIGNED>
<AMENDMENT_PROFILE>Y</AMENDMENT_PROFILE>
<WITH_TERMS>N</WITH_TERMS>
<IS_ATTACHED_DOC>Y</IS_ATTACHED_DOC>
<HEADER_SHORT_TEXT>
</HEADER_SHORT_TEXT>
<LINES>
<LINES_ROW>
<ITEM_REVISION>0</ITEM_REVISION>
<LINE_NUM>1</LINE_NUM>
<ITEM_DESCRIPTION>Jar Labelled EA Purity Perf P/Jelly 350ml</ITEM_DESCRIPTION>
<CANCEL_FLAG>Y</CANCEL_FLAG>
<UNIT_MEAS_LOOKUP_CODE>Each</UNIT_MEAS_LOOKUP_CODE>
<ORDER_TYPE_LOOKUP_CODE>QUANTITY</ORDER_TYPE_LOOKUP_CODE>
<UNIT_PRICE>1.31</UNIT_PRICE>
<QUANTITY>188032</QUANTITY>
<PO_HEADER_ID>711318</PO_HEADER_ID>
<PO_LINE_ID>1198098</PO_LINE_ID>
<ITEM_ID>114606</ITEM_ID>
<PRICE_TYPE_LOOKUP_CODE>FIXED</PRICE_TYPE_LOOKUP_CODE>
<CLOSED_CODE>OPEN</CLOSED_CODE>
<ORG_ID>1296</ORG_ID>
<QTY_RCV_TOLERANCE>0</QTY_RCV_TOLERANCE>
<OVER_TOLERANCE_ERROR_FLAG>WARNING</OVER_TOLERANCE_ERROR_FLAG>
<FIRM_STATUS_LOOKUP_CODE>N</FIRM_STATUS_LOOKUP_CODE>
<NEGOTIATED_BY_PREPARER_FLAG>N</NEGOTIATED_BY_PREPARER_FLAG>
<LAST_UPDATE_DATE>10-DEC-2009 17:42:27</LAST_UPDATE_DATE>
<LAST_UPDATED_BY>7794</LAST_UPDATED_BY>
<LINE_TYPE_ID>1</LINE_TYPE_ID>
<LAST_UPDATE_LOGIN>52339081</LAST_UPDATE_LOGIN>
<CREATION_DATE>10-DEC-2009 17:42:27</CREATION_DATE>
<CREATED_BY>7794</CREATED_BY>
<CATEGORY_ID>1935</CATEGORY_ID>
<LIST_PRICE_PER_UNIT>1.31</LIST_PRICE_PER_UNIT>
<TAX_NAME>Std Vat 14%</TAX_NAME>
<LINE_TYPE>QUANTITY</LINE_TYPE>
<PURCHASE_BASIS>GOODS</PURCHASE_BASIS>
<ITEM_NUM>53-60401-</ITEM_NUM>
<LINE_AMOUNT>246,321.92</LINE_AMOUNT>
<MATCHING_BASIS>QUANTITY</MATCHING_BASIS>
<PRICE_DIFF>
</PRICE_DIFF>
<LINE_SHORT_TEXT>
</LINE_SHORT_TEXT>
<LINE_LOCATIONS>
<LINE_LOCATIONS_ROW>
<SHIPMENT_NUM>1</SHIPMENT_NUM>
<DUE_DATE>22-JAN-2010 00:00:00</DUE_DATE>
<QUANTITY>188032</QUANTITY>
<PRICE_OVERRIDE>1.31</PRICE_OVERRIDE>
<QUANTITY_CANCELLED>0</QUANTITY_CANCELLED>
<TAXABLE_FLAG>Y</TAXABLE_FLAG>
<PO_HEADER_ID>711318</PO_HEADER_ID>
<PO_LINE_ID>1198098</PO_LINE_ID>
<LINE_LOCATION_ID>1107035</LINE_LOCATION_ID>
<SHIPMENT_TYPE>STANDARD</SHIPMENT_TYPE>
<CONSIGNED_FLAG>N</CONSIGNED_FLAG>
<RECEIVING_ROUTING_ID>2</RECEIVING_ROUTING_ID>
<ACCRUE_ON_RECEIPT_FLAG>Y</ACCRUE_ON_RECEIPT_FLAG>
<ORG_ID>1296</ORG_ID>
<INSPECTION_REQUIRED_FLAG>N</INSPECTION_REQUIRED_FLAG>
<RECEIPT_REQUIRED_FLAG>Y</RECEIPT_REQUIRED_FLAG>
<QTY_RCV_TOLERANCE>0</QTY_RCV_TOLERANCE>
<QTY_RCV_EXCEPTION_CODE>WARNING</QTY_RCV_EXCEPTION_CODE>
<ENFORCE_SHIP_TO_LOCATION_CODE>WARNING</ENFORCE_SHIP_TO_LOCATION_CODE>
<ALLOW_SUBSTITUTE_RECEIPTS_FLAG>N</ALLOW_SUBSTITUTE_RECEIPTS_FLAG>
<DAYS_EARLY_RECEIPT_ALLOWED>0</DAYS_EARLY_RECEIPT_ALLOWED>
<DAYS_LATE_RECEIPT_ALLOWED>0</DAYS_LATE_RECEIPT_ALLOWED>
<RECEIPT_DAYS_EXCEPTION_CODE>WARNING</RECEIPT_DAYS_EXCEPTION_CODE>
<INVOICE_CLOSE_TOLERANCE>0</INVOICE_CLOSE_TOLERANCE>
<RECEIVE_CLOSE_TOLERANCE>0</RECEIVE_CLOSE_TOLERANCE>
<SHIP_TO_ORGANIZATION_ID>1282</SHIP_TO_ORGANIZATION_ID>
<CLOSED_CODE>OPEN</CLOSED_CODE>
<ENCUMBERED_FLAG>N</ENCUMBERED_FLAG>
<APPROVED_FLAG>N</APPROVED_FLAG>
<LAST_UPDATE_DATE>10-DEC-2009 17:42:27</LAST_UPDATE_DATE>
<LAST_UPDATED_BY>7794</LAST_UPDATED_BY>
<LAST_UPDATE_LOGIN>52339081</LAST_UPDATE_LOGIN>
<CREATION_DATE>10-DEC-2009 17:42:27</CREATION_DATE>
<CREATED_BY>7794</CREATED_BY>
<QUANTITY_RECEIVED>0</QUANTITY_RECEIVED>
<QUANTITY_ACCEPTED>0</QUANTITY_ACCEPTED>
<QUANTITY_REJECTED>0</QUANTITY_REJECTED>
<QUANTITY_BILLED>0</QUANTITY_BILLED>
<UNIT_MEAS_LOOKUP_CODE>Each</UNIT_MEAS_LOOKUP_CODE>
<TAX_USER_OVERRIDE_FLAG>N</TAX_USER_OVERRIDE_FLAG>
<MATCH_OPTION>R</MATCH_OPTION>
<TAX_CODE_ID>10430</TAX_CODE_ID>
<CALCULATE_TAX_FLAG>N</CALCULATE_TAX_FLAG>
<VMI_FLAG>N</VMI_FLAG>
<AMOUNT>246,321.92</AMOUNT>
<AMOUNT_RECEIVED>0.00</AMOUNT_RECEIVED>
<AMOUNT_BILLED>0.00</AMOUNT_BILLED>
<AMOUNT_CANCELLED>0.00</AMOUNT_CANCELLED>
<AMOUNT_ACCEPTED>0.00</AMOUNT_ACCEPTED>
<AMOUNT_REJECTED>0.00</AMOUNT_REJECTED>
<DROP_SHIP_FLAG>N</DROP_SHIP_FLAG>
<SHIP_TO_LOCATION_ID>71695</SHIP_TO_LOCATION_ID>
<SHIP_TO_LOCATION_NAME>23M CS Isando Personal Care</SHIP_TO_LOCATION_NAME>
<SHIP_TO_ADDRESS_LINE1>23M CS Isando Personal</SHIP_TO_ADDRESS_LINE1>
<SHIP_TO_ADDRESS_LINE2>22 Purlin Road</SHIP_TO_ADDRESS_LINE2>
<SHIP_TO_ADDRESS_INFO>Isando, GP 1600</SHIP_TO_ADDRESS_INFO>
<SHIP_TO_COUNTRY>South Africa</SHIP_TO_COUNTRY>
<NEED_BY_DATE>22-JAN-2010 00:00:00</NEED_BY_DATE>
<LINE_LOC_SHORT_TEXT>
</LINE_LOC_SHORT_TEXT>
<DISTRIBUTIONS>
<DISTRIBUTIONS_ROW>
<AMOUNT_DELIVERED>0.00</AMOUNT_DELIVERED>
<AMOUNT_CANCELLED>0.00</AMOUNT_CANCELLED>
<DISTRIBUTION_TYPE>STANDARD</DISTRIBUTION_TYPE>
<PROJECT_ACCOUNTING_CONTEXT>No</PROJECT_ACCOUNTING_CONTEXT>
<ACCRUE_ON_RECEIPT_FLAG>Y</ACCRUE_ON_RECEIPT_FLAG>
<ORG_ID>1296</ORG_ID>
<DESTINATION_TYPE_CODE>INVENTORY</DESTINATION_TYPE_CODE>
<DESTINATION_ORGANIZATION_ID>1282</DESTINATION_ORGANIZATION_ID>
<ACCRUAL_ACCOUNT_ID>57175</ACCRUAL_ACCOUNT_ID>
<VARIANCE_ACCOUNT_ID>117936</VARIANCE_ACCOUNT_ID>
<PREVENT_ENCUMBRANCE_FLAG>N</PREVENT_ENCUMBRANCE_FLAG>
<PO_DISTRIBUTION_ID>1160340</PO_DISTRIBUTION_ID>
<LAST_UPDATE_DATE>10-DEC-2009 17:42:27</LAST_UPDATE_DATE>
<LAST_UPDATED_BY>7794</LAST_UPDATED_BY>
<PO_HEADER_ID>711318</PO_HEADER_ID>
<PO_LINE_ID>1198098</PO_LINE_ID>
<LINE_LOCATION_ID>1107035</LINE_LOCATION_ID>
<SET_OF_BOOKS_ID>1</SET_OF_BOOKS_ID>
<CODE_COMBINATION_ID>57172</CODE_COMBINATION_ID>
<QUANTITY_ORDERED>188032</QUANTITY_ORDERED>
<LAST_UPDATE_LOGIN>52339081</LAST_UPDATE_LOGIN>
<CREATION_DATE>10-DEC-2009 17:42:27</CREATION_DATE>
<CREATED_BY>7794</CREATED_BY>
<QUANTITY_DELIVERED>0</QUANTITY_DELIVERED>
<QUANTITY_BILLED>0</QUANTITY_BILLED>
<QUANTITY_CANCELLED>0</QUANTITY_CANCELLED>
<REQ_DISTRIBUTION_ID>1124422</REQ_DISTRIBUTION_ID>
<DELIVER_TO_LOCATION_ID>71695</DELIVER_TO_LOCATION_ID>
<DELIVER_TO_PERSON_ID>4585</DELIVER_TO_PERSON_ID>
<RATE_DATE>10-DEC-2009 00:00:00</RATE_DATE>
<AMOUNT_BILLED>0.00</AMOUNT_BILLED>
<ACCRUED_FLAG>N</ACCRUED_FLAG>
<ENCUMBERED_FLAG>N</ENCUMBERED_FLAG>
<RECOVERABLE_TAX>34,485.07</RECOVERABLE_TAX>
<NONRECOVERABLE_TAX>0.00</NONRECOVERABLE_TAX>
<RECOVERY_RATE>100.00</RECOVERY_RATE>
<DESTINATION_CONTEXT>INVENTORY</DESTINATION_CONTEXT>
<DISTRIBUTION_NUM>1</DISTRIBUTION_NUM>
<CHARGE_ACCOUNT>53-230-999-84-7220-0000</CHARGE_ACCOUNT>
<FULL_NAME>Mokoena, Johanna</FULL_NAME>
<EMAIL_ADDRESS>[email protected]</EMAIL_ADDRESS>
<REQUESTER_DELIVER_FIRST_NAME>Johanna</REQUESTER_DELIVER_FIRST_NAME>
<REQUESTER_DELIVER_LAST_NAME>Mokoena</REQUESTER_DELIVER_LAST_NAME>
</DISTRIBUTIONS_ROW>
</DISTRIBUTIONS>
</LINE_LOCATIONS_ROW>
</LINE_LOCATIONS>
</LINES_ROW>
</LINES>
<ADDRESS_DETAILS>
<ADDRESS_DETAILS_ROW>
<LOCATION_ID>71695</LOCATION_ID>
<ADDRESS_STYLE>ZA_GLB</ADDRESS_STYLE>
<ADDR_LABEL_1>Address Line 1</ADDR_LABEL_1>
<ADDR_LABEL_2>Address Line 2</ADDR_LABEL_2>
<ADDR_LABEL_3>Address Line 3</ADDR_LABEL_3>
<ADDR_LABEL_4>Address Line 4</ADDR_LABEL_4>
<ADDR_LABEL_5>Town / City</ADDR_LABEL_5>
<ADDR_LABEL_6>Postal Code</ADDR_LABEL_6>
<ADDR_LABEL_7>Province</ADDR_LABEL_7>
<ADDR_LABEL_8>Country</ADDR_LABEL_8>
<ADDR_DATA_1>23M CS Isando Personal</ADDR_DATA_1>
<ADDR_DATA_2>22 Purlin Road</ADDR_DATA_2>
<ADDR_DATA_5>Isando</ADDR_DATA_5>
<ADDR_DATA_6>1600</ADDR_DATA_6>
<ADDR_DATA_7>GP</ADDR_DATA_7>
<ADDR_DATA_8>ZA</ADDR_DATA_8>
</ADDRESS_DETAILS_ROW>
<ADDRESS_DETAILS_ROW>
<LOCATION_ID>78573</LOCATION_ID>
<ADDRESS_STYLE>ZA_GLB</ADDRESS_STYLE>
<ADDR_LABEL_1>Address Line 1</ADDR_LABEL_1>
<ADDR_LABEL_2>Address Line 2</ADDR_LABEL_2>
<ADDR_LABEL_3>Address Line 3</ADDR_LABEL_3>
<ADDR_LABEL_4>Address Line 4</ADDR_LABEL_4>
<ADDR_LABEL_5>Town / City</ADDR_LABEL_5>
<ADDR_LABEL_6>Postal Code</ADDR_LABEL_6>
<ADDR_LABEL_7>Province</ADDR_LABEL_7>
<ADDR_LABEL_8>Country</ADDR_LABEL_8>
<ADDR_DATA_1>P O Box 527</ADDR_DATA_1>
<ADDR_DATA_5>Paarl</ADDR_DATA_5>
<ADDR_DATA_6>7620</ADDR_DATA_6>
<ADDR_DATA_8>ZA</ADDR_DATA_8>
</ADDRESS_DETAILS_ROW>
<ADDRESS_DETAILS_ROW>
<LOCATION_ID>71715</LOCATION_ID>
<ADDRESS_STYLE>ZA_GLB</ADDRESS_STYLE>
<ADDR_LABEL_1>Address Line 1</ADDR_LABEL_1>
<ADDR_LABEL_2>Address Line 2</ADDR_LABEL_2>
<ADDR_LABEL_3>Address Line 3</ADDR_LABEL_3>
<ADDR_LABEL_4>Address Line 4</ADDR_LABEL_4>
<ADDR_LABEL_5>Town / City</ADDR_LABEL_5>
<ADDR_LABEL_6>Postal Code</ADDR_LABEL_6>
<ADDR_LABEL_7>Province</ADDR_LABEL_7>
<ADDR_LABEL_8>Country</ADDR_LABEL_8>
<ADDR_DATA_1>Corporate Hill Office Park</ADDR_DATA_1>
<ADDR_DATA_2>William Nicholl Drive</ADDR_DATA_2>
<ADDR_DATA_5>Bryanston</ADDR_DATA_5>
<ADDR_DATA_6>1768</ADDR_DATA_6>
<ADDR_DATA_7>GP</ADDR_DATA_7>
<ADDR_DATA_8>ZA</ADDR_DATA_8>
</ADDRESS_DETAILS_ROW>
<ADDRESS_DETAILS_ROW>
<LOCATION_ID>71699</LOCATION_ID>
<ADDRESS_STYLE>ZA_GLB</ADDRESS_STYLE>
<ADDR_LABEL_1>Address Line 1</ADDR_LABEL_1>
<ADDR_LABEL_2>Address Line 2</ADDR_LABEL_2>
<ADDR_LABEL_3>Address Line 3</ADDR_LABEL_3>
<ADDR_LABEL_4>Address Line 4</ADDR_LABEL_4>
<ADDR_LABEL_5>Town / City</ADDR_LABEL_5>
<ADDR_LABEL_6>Postal Code</ADDR_LABEL_6>
<ADDR_LABEL_7>Province</ADDR_LABEL_7>
<ADDR_LABEL_8>Country</ADDR_LABEL_8>
<ADDR_DATA_1>Coprporate Hill Office Park</ADDR_DATA_1>
<ADDR_DATA_2>Willima Nicholl Drive</ADDR_DATA_2>
<ADDR_DATA_5>Bryanston</ADDR_DATA_5>
<ADDR_DATA_6>1768</ADDR_DATA_6>
<ADDR_DATA_7>GP</ADDR_DATA_7>
<ADDR_DATA_8>ZA</ADDR_DATA_8>
</ADDRESS_DETAILS_ROW>
</ADDRESS_DETAILS>
</PO_DATA>
I'm really stumped. I tried using the choose when clause but it doesn't work as I think it isreading the wrong cancel flag.
Any help will be much appreciated.
Thanks, Ash

have to see your for-each statements.
and you can do it, by using .. to go up one level
example from current level to go up4 level up ../../../../CUSTOM_FLAG
../../../CUSTOM_FLAG three lvl up.
Need to know the cancel_flag element you said, i can see only one :) in the given xml.

Cancel_flag in PO Output for Communication report

I'm trying to build logic into an RTF template for the "PO Output for Communication" report to handle cancelled lines. The cancel_flag can be set to "Y" at any of 3 levels - PO Header, PO Line and PO shipment. The field is called the same thing (cancel_flag) at all 3 levels but it doesn't always exist at all 3 levels. What do I call the field in my "IF" statement, so that it is looking at the correct field? Right now, if I am at the line level and I want to check the cancel_flag, if it doesn't exist, it looks at the cancel_flag at the shipment level.

have to see your for-each statements.
and you can do it, by using .. to go up one level
example from current level to go up4 level up ../../../../CUSTOM_FLAG
../../../CUSTOM_FLAG three lvl up.
Need to know the cancel_flag element you said, i can see only one :) in the given xml.

EDI Output ZB00 not getting determined in case of Split Deliveries.

Hello All,
A very Good Morning to you,
Hope you are doing good,
We have come across one critical Issue where the EDI Output ZB00 Dispatch Advice is not getting determined in case of few Split Deliveries in PROD.
Issue : On a daily basis our Client is generating Split Delivery Process used for some specific customers only.
These specific customers we are maintaining in ZPARAMS Table. The Flow of the Process is as below.
Sales Order -->Parent Delivery ZLF--> Split Delivery ZLS--> Invoice ZF2.
First the Sales Order ZOR is created through VA01 or EDI.
This ZOR is processed via ZVL10A to create parent delivery ZLF.
Once the parent delivery ZLF is created an Outbound IDoc SHPOD gets triggered which goes to the Distribution Centre Technicolor UK to check the confirmed qty and materials that needs to be delivered.
Once the Quantity is verified and confirmed from DC an Inbound IDoc SHCON interface SAP.
This Inbound SHPCON IDoc checks the entry in ZPARAMS for that customer. If the entry is found it creates one more Split Delivery ZLS doing picking and post Goods Issue in one step. This is the point where the ZB00 output is determined automatically in ZLS Delivery and processed successfully immediately.
After that the Normal Invoice ZF2 is created.
We have given the process flow details in the attachment along with Functional Modules used by the EDI Team.
Now the Issue we are currently facing on a daily basis in PRD Out of the Total Count of ZLS Deliveries in few of ZLS Deliveries ZB00 Output is not getting determined at all which is causing a huge revenue loss. For remaining ZLS Deliveries it is getting determined correctly and processed.For Split Delivery we have only 2 Customers.
We would like to know why this is happening in case of only few ZLS Deliveries.
As a work around we have just write one program for these disputed deliveries where it will go in VL02N of these deliveries and save it without doing any changes. This will make ZB00 determined and processed immediately.
We have even check the scenario in Quality Client no Issues at all. It is getting determined and processed successfully for all the test cases we created.
Please could you help us on this so that we can fix this critical Issue.
Many Thanks,
Farhan.

if QA system works correct
you probably need to find the difference between it and PRD client.
I guess it is a huge job.
but who does if not you?
because you have a lot of custom things included coding
also request abaper.

Sorting of PO Line Attachments in PO Output for Communication

Hi,
I have created a RTF template to generate PDF output of the "PO Output for Communication" program. The Short text and Long Text attachments of PO Line are appearing correctly but not in the same sequence as user has entered in the Purchase Order.
Example:
PO# - 4444
Po Line Attachments entered by user and this is the expected output as well:
Seq 10: Short Text1
Seq 20: Long Text1
Seq 30: Short Text2
Seq 40: Long Text2
Present Report Output:
PO# - 4444
PO Line Attachments:
Short Text1
Short Text2
Long Text1
Long Text2
Actually the Short Text and Long Text attachments are generated as follows:
<?xml version="1.0" encoding="UTF-8"?>
<PO_DATA>
<TYPE_LOOKUP_CODE>STANDARD</TYPE_LOOKUP_CODE>
<SEGMENT1>24687</SEGMENT1>
<REVISION_NUM>0</REVISION_NUM>
<PRINT_COUNT>3</PRINT_COUNT>
<CREATION_DATE>29-APR-2009 14:28:52</CREATION_DATE>
<NOTE_TO_VENDOR>this is a test po to supplier in terms window</NOTE_TO_VENDOR>
<DOCUMENT_BUYER_FIRST_NAME>Sanjay</DOCUMENT_BUYER_FIRST_NAME>
<DOCUMENT_BUYER_LAST_NAME>Kumar</DOCUMENT_BUYER_LAST_NAME>
<DOCUMENT_BUYER_AGENT_ID>8756</DOCUMENT_BUYER_AGENT_ID>
<CANCEL_FLAG>N</CANCEL_FLAG>
<CONFIRMING_ORDER_FLAG>N</CONFIRMING_ORDER_FLAG>
<ACCEPTANCE_REQUIRED_FLAG>N</ACCEPTANCE_REQUIRED_FLAG>
<CURRENCY_CODE>USD</CURRENCY_CODE>
<CURRENCY_NAME>US dollar</CURRENCY_NAME>
<PAYMENT_TERMS>NET 30</PAYMENT_TERMS>
<CUSTOMER_NUM>1244</CUSTOMER_NUM>
<VENDOR_NUM>RR10</VENDOR_NUM>
<VENDOR_NAME>OFFICE DEPOT</VENDOR_NAME>
<VENDOR_ADDRESS_LINE1>PO BOX 31533</VENDOR_ADDRESS_LINE1>
<VENDOR_CITY>HARTFORD</VENDOR_CITY>
<VENDOR_STATE>CT</VENDOR_STATE>
<VENDOR_POSTAL_CODE>06150-1533</VENDOR_POSTAL_CODE>
<SHIP_TO_LOCATION_ID>88</SHIP_TO_LOCATION_ID>
<SHIP_TO_LOCATION_NAME>US CORPORATE HDQTRS</SHIP_TO_LOCATION_NAME>
<SHIP_TO_ADDRESS_LINE1>123 JFK RD</SHIP_TO_ADDRESS_LINE1>
<SHIP_TO_ADDRESS_INFO>Broadway, WA 02421</SHIP_TO_ADDRESS_INFO>
<SHIP_TO_COUNTRY>United States</SHIP_TO_COUNTRY>
<BILL_TO_LOCATION_ID>88</BILL_TO_LOCATION_ID>
<BILL_TO_LOCATION_NAME>US CORPORATE HDQTRS</BILL_TO_LOCATION_NAME>
<BILL_TO_ADDRESS_LINE1>123 JFK RD</BILL_TO_ADDRESS_LINE1>
<BILL_TO_ADDRESS_INFO>Broadway, WA 02421</BILL_TO_ADDRESS_INFO>
<BILL_TO_COUNTRY>United States</BILL_TO_COUNTRY>
<ATTRIBUTE1>MA</ATTRIBUTE1>
<VENDOR_SITE_ID>9983</VENDOR_SITE_ID>
<PO_HEADER_ID>27162</PO_HEADER_ID>
<APPROVED_FLAG>N</APPROVED_FLAG>
<VENDOR_ID>826</VENDOR_ID>
<ORG_ID>29</ORG_ID>
<COMMENTS>Test PO to test template</COMMENTS>
<FIRM_STATUS_LOOKUP_CODE>N</FIRM_STATUS_LOOKUP_CODE>
<FROZEN_FLAG>N</FROZEN_FLAG>
<CREATED_BY>3349</CREATED_BY>
<TERMS_ID>10001</TERMS_ID>
<RATE_DATE>29-APR-2009 00:00:00</RATE_DATE>
<AUTHORIZATION_STATUS>N</AUTHORIZATION_STATUS>
<NOTE_TO_RECEIVER>this is a test po to receiver in terms window</NOTE_TO_RECEIVER>
<LAST_UPDATE_DATE>29-APR-2009 14:30:52</LAST_UPDATE_DATE>
<LAST_UPDATED_BY>3349</LAST_UPDATED_BY>
<SUMMARY_FLAG>N</SUMMARY_FLAG>
<ENABLED_FLAG>Y</ENABLED_FLAG>
<LAST_UPDATE_LOGIN>1250381</LAST_UPDATE_LOGIN>
<SUPPLY_AGREEMENT_FLAG>N</SUPPLY_AGREEMENT_FLAG>
<PENDING_SIGNATURE_FLAG>N</PENDING_SIGNATURE_FLAG>
<OU_NAME>ABC LTD</OU_NAME>
<OU_ADDR1>123 JFK RD</OU_ADDR1>
<OU_TOWN_CITY>Broadway</OU_TOWN_CITY>
<OU_REGION2>WA</OU_REGION2>
<OU_POSTALCODE>44421</OU_POSTALCODE>
<OU_COUNTRY>United States</OU_COUNTRY>
<BUYER_ADDRESS_LINE1>123 JFK RD</BUYER_ADDRESS_LINE1>
<BUYER_CITY_STATE_ZIP>Broadway, WA 44421</BUYER_CITY_STATE_ZIP>
<BUYER_CONTACT_PHONE>322-445-4533</BUYER_CONTACT_PHONE>
<TOTAL_AMOUNT>6,000.00</TOTAL_AMOUNT>
<BUYER_COUNTRY>United States</BUYER_COUNTRY>
<DOCUMENT_CREATION_METHOD>ENTER_PO</DOCUMENT_CREATION_METHOD>
<DOCUMENT_TYPE>Standard Purchase Order</DOCUMENT_TYPE>
<COVER_MESSAGE>This document has important legal consequences. </COVER_MESSAGE>
<AMMENDMENT_MESSAGE>This document has important legal consequences.
</AMMENDMENT_MESSAGE>
<TEST_FLAG>D</TEST_FLAG>
<DIST_SHIPMENT_COUNT>1</DIST_SHIPMENT_COUNT>
<DOCUMENT_NAME>Standard Purchase Order 24687, 0</DOCUMENT_NAME>
<SIGNED>F</SIGNED>
<AMENDMENT_PROFILE>Y</AMENDMENT_PROFILE>
<WITH_TERMS>N</WITH_TERMS>
<IS_ATTACHED_DOC>Y</IS_ATTACHED_DOC>
<MESSAGE>
<MESSAGE_ROW>
<MESSAGE>PO_FO_AGREEMENT_CANCELED</MESSAGE>
<TEXT>This agreement CANCELED on</TEXT>
</MESSAGE_ROW>
<MESSAGE_ROW>
<MESSAGE>PO_WF_NOTIF_VENDOR_NO</MESSAGE>
<TEXT>Supplier No.</TEXT>
</MESSAGE_ROW>
</MESSAGE>
<HEADER_SHORT_TEXT>
</HEADER_SHORT_TEXT>
<LINES>
<LINES_ROW>
<LINE_NUM>1</LINE_NUM>
<ITEM_DESCRIPTION>test po</ITEM_DESCRIPTION>
<CANCEL_FLAG>N</CANCEL_FLAG>
<NOTE_TO_VENDOR>This is a test PO. do not ship.</NOTE_TO_VENDOR>
<UNIT_MEAS_LOOKUP_CODE>Unit</UNIT_MEAS_LOOKUP_CODE>
<ORDER_TYPE_LOOKUP_CODE>QUANTITY</ORDER_TYPE_LOOKUP_CODE>
<ATTRIBUTE1>N</ATTRIBUTE1>
<UNIT_PRICE>5000</UNIT_PRICE>
<QUANTITY>1</QUANTITY>
<PO_HEADER_ID>27162</PO_HEADER_ID>
<PO_LINE_ID>53995</PO_LINE_ID>
<ORG_ID>29</ORG_ID>
<UNORDERED_FLAG>N</UNORDERED_FLAG>
<CLOSED_FLAG>N</CLOSED_FLAG>
<TAXABLE_FLAG>N</TAXABLE_FLAG>
<CAPITAL_EXPENSE_FLAG>N</CAPITAL_EXPENSE_FLAG>
<NEGOTIATED_BY_PREPARER_FLAG>N</NEGOTIATED_BY_PREPARER_FLAG>
<LAST_UPDATE_DATE>29-APR-2009 14:29:36</LAST_UPDATE_DATE>
<LAST_UPDATED_BY>3349</LAST_UPDATED_BY>
<LINE_TYPE_ID>1000</LINE_TYPE_ID>
<LAST_UPDATE_LOGIN>1250381</LAST_UPDATE_LOGIN>
<CREATION_DATE>29-APR-2009 14:28:52</CREATION_DATE>
<CREATED_BY>3349</CREATED_BY>
<CATEGORY_ID>224</CATEGORY_ID>
<ALLOW_PRICE_OVERRIDE_FLAG>N</ALLOW_PRICE_OVERRIDE_FLAG>
<LIST_PRICE_PER_UNIT>5000</LIST_PRICE_PER_UNIT>
<LINE_TYPE>QUANTITY</LINE_TYPE>
<PURCHASE_BASIS>GOODS</PURCHASE_BASIS>
<LINE_AMOUNT>5,000.00</LINE_AMOUNT>
<MANUAL_PRICE_CHANGE_FLAG>N</MANUAL_PRICE_CHANGE_FLAG>
<MATCHING_BASIS>QUANTITY</MATCHING_BASIS>
<PRICE_DIFF>
</PRICE_DIFF>
*<LINE_SHORT_TEXT>*
*<LINE_SHORT_TEXT_ROW>*
*<PO_LINE_ID>53995</PO_LINE_ID>*
*<SHORT_TEXT>Short Text1</SHORT_TEXT>*
*</LINE_SHORT_TEXT_ROW>*
*<LINE_SHORT_TEXT_ROW>*
*<PO_LINE_ID>53995</PO_LINE_ID>*
*<SHORT_TEXT>Short Text2</SHORT_TEXT>*
*</LINE_SHORT_TEXT_ROW>*
*</LINE_SHORT_TEXT>*
<LINE_LOCATIONS>
<LINE_LOCATIONS_ROW>
<SHIPMENT_NUM>1</SHIPMENT_NUM>
<DUE_DATE>15-MAY-2009 00:00:00</DUE_DATE>
<QUANTITY>1</QUANTITY>
<PRICE_OVERRIDE>5000</PRICE_OVERRIDE>
<QUANTITY_CANCELLED>0</QUANTITY_CANCELLED>
<CANCEL_FLAG>N</CANCEL_FLAG>
<TAXABLE_FLAG>N</TAXABLE_FLAG>
<PO_HEADER_ID>27162</PO_HEADER_ID>
<PO_LINE_ID>53995</PO_LINE_ID>
<LINE_LOCATION_ID>53678</LINE_LOCATION_ID>
<SHIPMENT_TYPE>STANDARD</SHIPMENT_TYPE>
<RECEIVING_ROUTING_ID>3</RECEIVING_ROUTING_ID>
<ACCRUE_ON_RECEIPT_FLAG>N</ACCRUE_ON_RECEIPT_FLAG>
<ORG_ID>29</ORG_ID>
<RECEIPT_REQUIRED_FLAG>N</RECEIPT_REQUIRED_FLAG>
<QTY_RCV_TOLERANCE>10</QTY_RCV_TOLERANCE>
<QTY_RCV_EXCEPTION_CODE>WARNING</QTY_RCV_EXCEPTION_CODE>
<ENFORCE_SHIP_TO_LOCATION_CODE>NONE</ENFORCE_SHIP_TO_LOCATION_CODE>
<ALLOW_SUBSTITUTE_RECEIPTS_FLAG>N</ALLOW_SUBSTITUTE_RECEIPTS_FLAG>
<DAYS_EARLY_RECEIPT_ALLOWED>5</DAYS_EARLY_RECEIPT_ALLOWED>
<DAYS_LATE_RECEIPT_ALLOWED>5</DAYS_LATE_RECEIPT_ALLOWED>
<RECEIPT_DAYS_EXCEPTION_CODE>WARNING</RECEIPT_DAYS_EXCEPTION_CODE>
<INVOICE_CLOSE_TOLERANCE>2</INVOICE_CLOSE_TOLERANCE>
<RECEIVE_CLOSE_TOLERANCE>100</RECEIVE_CLOSE_TOLERANCE>
<SHIP_TO_ORGANIZATION_ID>208</SHIP_TO_ORGANIZATION_ID>
<CLOSED_CODE>OPEN</CLOSED_CODE>
<LAST_ACCEPT_DATE>09-MAY-2009 00:00:00</LAST_ACCEPT_DATE>
<ENCUMBERED_FLAG>N</ENCUMBERED_FLAG>
<FIRM_STATUS_LOOKUP_CODE>N</FIRM_STATUS_LOOKUP_CODE>
<LAST_UPDATE_DATE>29-APR-2009 14:31:31</LAST_UPDATE_DATE>
<LAST_UPDATED_BY>3349</LAST_UPDATED_BY>
<LAST_UPDATE_LOGIN>1250381</LAST_UPDATE_LOGIN>
<CREATION_DATE>29-APR-2009 14:28:53</CREATION_DATE>
<CREATED_BY>3349</CREATED_BY>
<QUANTITY_RECEIVED>0</QUANTITY_RECEIVED>
<QUANTITY_ACCEPTED>0</QUANTITY_ACCEPTED>
<QUANTITY_REJECTED>0</QUANTITY_REJECTED>
<QUANTITY_BILLED>0</QUANTITY_BILLED>
<UNIT_MEAS_LOOKUP_CODE>Unit</UNIT_MEAS_LOOKUP_CODE>
<TAX_USER_OVERRIDE_FLAG>N</TAX_USER_OVERRIDE_FLAG>
<MATCH_OPTION>P</MATCH_OPTION>
<CALCULATE_TAX_FLAG>Y</CALCULATE_TAX_FLAG>
<NOTE_TO_RECEIVER>this is a note in shipments receiver</NOTE_TO_RECEIVER>
<AMOUNT>5,000.00</AMOUNT>
<SHIP_TO_LOCATION_ID>88</SHIP_TO_LOCATION_ID>
<SHIP_TO_LOCATION_NAME>US CORPORATE HDQTRS</SHIP_TO_LOCATION_NAME>
<SHIP_TO_ADDRESS_LINE1>123 JFK RD</SHIP_TO_ADDRESS_LINE1>
<SHIP_TO_ADDRESS_INFO>Broadway, WA 02421</SHIP_TO_ADDRESS_INFO>
<SHIP_TO_COUNTRY>United States</SHIP_TO_COUNTRY>
<NEED_BY_DATE>15-MAY-2009 00:00:00</NEED_BY_DATE>
<PROMISED_DATE>04-MAY-2009 00:00:00</PROMISED_DATE>
<LINE_LOC_SHORT_TEXT>
</LINE_LOC_SHORT_TEXT>
<DISTRIBUTIONS>
<DISTRIBUTIONS_ROW>
<DISTRIBUTION_TYPE>STANDARD</DISTRIBUTION_TYPE>
<ACCRUE_ON_RECEIPT_FLAG>N</ACCRUE_ON_RECEIPT_FLAG>
<ORG_ID>29</ORG_ID>
<DESTINATION_TYPE_CODE>EXPENSE</DESTINATION_TYPE_CODE>
<DESTINATION_ORGANIZATION_ID>208</DESTINATION_ORGANIZATION_ID>
<ACCRUAL_ACCOUNT_ID>1037</ACCRUAL_ACCOUNT_ID>
<VARIANCE_ACCOUNT_ID>22148</VARIANCE_ACCOUNT_ID>
<PREVENT_ENCUMBRANCE_FLAG>N</PREVENT_ENCUMBRANCE_FLAG>
<PO_DISTRIBUTION_ID>55228</PO_DISTRIBUTION_ID>
<LAST_UPDATE_DATE>29-APR-2009 14:32:23</LAST_UPDATE_DATE>
<LAST_UPDATED_BY>3349</LAST_UPDATED_BY>
<PO_HEADER_ID>27162</PO_HEADER_ID>
<PO_LINE_ID>53995</PO_LINE_ID>
<LINE_LOCATION_ID>53678</LINE_LOCATION_ID>
<SET_OF_BOOKS_ID>25</SET_OF_BOOKS_ID>
<CODE_COMBINATION_ID>22148</CODE_COMBINATION_ID>
<QUANTITY_ORDERED>1</QUANTITY_ORDERED>
<LAST_UPDATE_LOGIN>1250381</LAST_UPDATE_LOGIN>
<CREATION_DATE>29-APR-2009 14:28:54</CREATION_DATE>
<CREATED_BY>3349</CREATED_BY>
<QUANTITY_DELIVERED>0</QUANTITY_DELIVERED>
<QUANTITY_BILLED>0</QUANTITY_BILLED>
<QUANTITY_CANCELLED>0</QUANTITY_CANCELLED>
<DELIVER_TO_LOCATION_ID>89</DELIVER_TO_LOCATION_ID>
<DELIVER_TO_PERSON_ID>5324</DELIVER_TO_PERSON_ID>
<RATE_DATE>29-APR-2009 00:00:00</RATE_DATE>
<ENCUMBERED_FLAG>N</ENCUMBERED_FLAG>
<RECOVERY_RATE>0.00</RECOVERY_RATE>
<TAX_RECOVERY_OVERRIDE_FLAG>N</TAX_RECOVERY_OVERRIDE_FLAG>
<DESTINATION_CONTEXT>EXPENSE</DESTINATION_CONTEXT>
<DISTRIBUTION_NUM>1</DISTRIBUTION_NUM>
<CHARGE_ACCOUNT>05-3002-7050-000-000</CHARGE_ACCOUNT>
<FULL_NAME>Devine, Alison</FULL_NAME>
<EMAIL_ADDRESS>[email protected]</EMAIL_ADDRESS>
<REQUESTER_DELIVER_FIRST_NAME>Karen</REQUESTER_DELIVER_FIRST_NAME>
<REQUESTER_DELIVER_LAST_NAME>MA</REQUESTER_DELIVER_LAST_NAME>
</DISTRIBUTIONS_ROW>
</DISTRIBUTIONS>
</LINE_LOCATIONS_ROW>
</LINE_LOCATIONS>
</LINES_ROW>
</LINES>
*<LINE_ATTACHMENTS>*
*<TEXT>Long Text1</TEXT>*
*<ID>53995</ID>*
*<TEXT>Long Text2</TEXT>*
*<ID>53995</ID>*
*</LINE_ATTACHMENTS>*
<ADDRESS_DETAILS>
<ADDRESS_DETAILS_ROW>
<LOCATION_ID>88</LOCATION_ID>
<ADDRESS_STYLE>US_GLB</ADDRESS_STYLE>
<ADDR_LABEL_1>Address Line1</ADDR_LABEL_1>
<ADDR_LABEL_2>Address Line2</ADDR_LABEL_2>
<ADDR_LABEL_3>Address Line3</ADDR_LABEL_3>
<ADDR_LABEL_4>City</ADDR_LABEL_4>
<ADDR_LABEL_5>County</ADDR_LABEL_5>
<ADDR_LABEL_6>State</ADDR_LABEL_6>
<ADDR_LABEL_7>Zip Code</ADDR_LABEL_7>
<ADDR_LABEL_8>Country</ADDR_LABEL_8>
<ADDR_LABEL_9>Telephone</ADDR_LABEL_9>
<ADDR_LABEL_10>Fax</ADDR_LABEL_10>
<ADDR_LABEL_11>Sales Tax Override</ADDR_LABEL_11>
<ADDR_LABEL_12>Inside City Limits</ADDR_LABEL_12>
<ADDR_DATA_1>123 JFK RD</ADDR_DATA_1>
<ADDR_DATA_4>Broadway</ADDR_DATA_4>
<ADDR_DATA_6>WA</ADDR_DATA_6>
<ADDR_DATA_7>33444</ADDR_DATA_7>
<ADDR_DATA_8>US</ADDR_DATA_8>
<ADDR_DATA_9>322-588-4534</ADDR_DATA_9>
</ADDRESS_DETAILS_ROW>
</ADDRESS_DETAILS>
</PO_DATA>
Can you please advice whether we can have the attachments as user entered in the Purchase Order.
Thanks for your help.
Pranit.

See...
http://blogs.oracle.com/xmlpublisher/2008/07/po_line_description_quandary.html

EDI Output type

Hi guys
I have configured the EDI output type in the system and assigned to the procedure but when i am creating the sales order the system is not picking the procedure and when i pick it manually and try saving then it gives me error "Maintain outgoing EDI connection data for partner". I am manitaining records in VV11
Where do i maintain the connection data???

Hi,
RFC Destination : SM59
Partner Profile : WE20
Port Definition : WE21
Go through the following links:
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDISC/CAEDISCAP_STC.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDI/CAEDI.pdf
http://www.sapgenie.com/sapedi/index.htm
Hope this will help.
Regards,
Naveen.

EDI/IDocs for WMS

Hi all,
I need sample code and processing steps for EDI-IDocs for WMS concept.

Hi,
check this it wil be helpful to you.
Electronic Data Interchange
Cross-company exchange of electronic data (for example business documents) between domestic and international business partners who use a variety of hardware, software, and communication services. The data involved is formatted according to predefined standards. In addition to this, SAP ALE technology is available for data exchange within a company.
Refer
http://www.erpgenie.com/sapedi/index.htm
http://help.sap.com/saphelp_nw04/helpdata/en/72/c18ee5546a11d182cc0000e829fbfe/frameset.htm
https://www.2020software.com/products/Fourth_Shift_Edition_for_SAP_Business_One_Electronic_Data_Interchange.asp
http://downloads-zdnet.com.com/SoftwareandWebDevelopment/SoftwareDevelopmentTools/ElectronicData+Interchange/
http://www.erpgenie.com/sapedi/index.htm
http://www.kostal.com/english/downloads/EDI_AGB_eng.pdfd
EDI FLOW :
Here is some thing which helps you and here the purchase order is taken as example too..
Electronic Data Interchange, or EDI, is the electronic exchange of business data. Using a standard format, EDI provides a method of transmitting business data from one computer to another, without the need to re-key data. This electronic link can result in more effective business transactions. With EDI, paper documents such as invoices can be replaced with electronic transmissions, thus time is saved, and the potential for error is minimized. Data can be exchanged at any time. Related business expenses, such as postage, printing, phone calls, and handling, can also be significantly reduced. EDI can aid in the support of manufacturing efforts, such as Just-in-Time and Third Party Warehousing, and financial efforts, such as Electronic Payments.
What parts of the business cycle can be supported by EDI?
Any business documents that are currently exchanged using paper can be converted to an EDI. Standards. Standards include ANSI X12 and XML/EDI are primarily used in the United States, while EDIFACT is used in Europe and Asia.
How does EDI get started?
EDI gets started when one company contacts another expressing interest in trading business documents electronically using Electronic Data Interchange. The two companies must first determine each other's EDI capabilities. If you do not already know your EDI capabilities, we have prepared a questionnaire to help you determine them. If you are already EDI capable, we will coordinate with your technical staff to determine a testing plan. Upon completion of testing the EDI documents, the appropriate business personnel will set a production start date to begin the exchange of EDI business data. If you are not EDI capable, we recommend you first obtain a commitment from your upper management. Your company will need to allocate resources and capital for software, hardware, testing, possible programming, and training.
What is the flow of EDI?
The flow of EDI depends on the sophistication of your systems and your EDI software. If you have internal purchasing/order entry systems, you will need interface programs that can extract and insert data out of and into these systems. EDI programs that interface with your internal systems are preferred over software that requires re-keying of data. Embassy Software specializes in seemless interface between EDI and your back office systems. Using a purchase order as an example of a business document your customer would send that PO electronically (850) to you. It could be sent either through a VAN (Value Added Network) or through an FTP server. You would take that 850 and convert it either into and ODBC database, a flat file or XML document to be imported into your Order System with the use of EDI Software such as PassportXchange.. Using EDI communication software, which is part of the PassportXchange package you would pull down data at set intervals from the VAN or FTP. These documents are then processed through EDI translation software and output to our order entry system. Finally, an EDI document called a functional acknowledgment (997) is sent to your customer.
check this.
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://www.sapgenie.com/sapedi/index.htm
http://help.sap.com/saphelp_nw04/helpdata/en/72/c18ee5546a11d182cc0000e829fbfe/frameset.htm
https://www.2020software.com/products/Fourth_Shift_Edition_for_SAP_Business_One_Electronic_Data_Interchange.asp
http://downloads-zdnet.com.com/SoftwareandWebDevelopment/SoftwareDevelopmentTools/ElectronicData+Interchange/
http://www.erpgenie.com/sapedi/index.htm
http://www.kostal.com/english/downloads/EDI_AGB_eng.pdfd
cheers,
sowjanya.

EDI steps for salesorder

Hi
Please can anybody help me with the steps to configure EDI output type for VA01/VA02 (Sales order create /change) . The requirement is to generate Idoc every time a sales order is created or modified.
Thanks in advance

Hi
Please can anybody help me with the steps to configure EDI output type for VA01/VA02 (Sales order create /change) . The requirement is to generate Idoc every time a sales order is created or modified.
Thanks in advance

MM I need to inform in the idoc output when you cancel a document.

hi i need to know how to report on a idoc cancels out when the framework contract and a service entrance (ML81N, ME31K) is that when you cancel a document does not create logistical message. Thanks
I need to inform in the idoc output when you cancel a document OF ml81n migo or me31k, if you create or modify a documet of ml81n migo or me31k , logistical message is generated but not nullify. Is there any way to report a cancellation in the output idoc?
Edited by: juliansantelli on Apr 7, 2011 4:26 PM

Sorry, good network connection, happily downloaded for 15 minutes before this popup appeared... Staying with iOS 5.1.1 for now hoping Apple can sort it..oO

Problem in triggerring EDI idoc for Purchase order..

Hi experts,
I am trying to create an outbound EDI IDOC for a PO.
I have configured the partner profile in partner type LI with message type ORDERS in outbound parameters. I have created a new output type ZEDI for EDI, and entered in a message control, as application EF, message type ZEDI and process code ME10.
But when i go to the me23n and goto--> messages, but when i click F4 for output type i am not able to see the new output type ZEDI i have created.
And if i also enter NEU with medium EDI, and Partner function VN, and partner 3000(where i configured the parnter profiles), its giving an error as, "maintain outgoing EDI-connection data for partner 3000".
Kindly help me out. please experts reply me..
Nithin

Hi
<b>In the transaction NACE</b>
you need to maintain the necessary 'Z' output type, in your case.
Hope this will help.
Please reward suitable points.
Regards
- Atul

EDI output for PO cancellation

Similar Messages

Maybe you are looking for