EDI Output not triggerring

Hi,
I have created an output ZINL in NACE tcode to generate an IDoc assigned partner type LS. This output should be automatically assigned when i change any invoice list (VF22). Parnter name is ZLSPAR. Logical system ZLSPAR was created first in BD54 and then it was created as a LS partner type in WE20.
The condition record i created in VF31 is of the key combination Sales area+Bill doc type. The bill doc type is also assigned with LS partner and respective partner name.
There is one VOFM requirement created for the output, which is passed successfully. Inspite of this, ZINL output is not getting automatically assigned in VF22 tcode.
Is there anything else i need to be doing?
Thanks
Vish

Hi,
check the artilce for the configurations to be done in EDI.
http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/d4ce58df-0901-0010-a4be-9ae9eda61107
This is related to PO and Not Invoices though but could come in useful.
cheers
Aveek

Similar Messages

PO change output not triggered after deletion of line item

Hello SAP experts,
I have one issue with PO output
I have created PO with output type & we are outputing through ME9F( 3- Send with application own transaction)
Below is the sequence,
1.PO created & outputed thru ME9F
2.Now ,i added the line item in the PO,Output triggred but not processed.
3.I deleted the line item immedietely,Output not triggered.
(My question is Why the output is not tiggered?)
4.I outputed it through ME9F,vendor will receive only 1st output & never get the 2nd o/p for the deletion of item.
I am clear that after processsing the 1st output,then only i can process the 2nd.
But in business point of view,this scene created the problem.
Please provide your valuable input.

Hi,
In IMG - Materials Management- Purchasing-Messages - Fields relevant to Print out of changes
Enter Table EKPO , Reference Field LOEKZ, tick on change print relevant for purchase order,in routine enter 03.
Now your Output will be triggered with a change indicator and you can process it using ME9F.
Regards
Chandra Shekhar

Shipment output not triggered...

Hi, I tried to find solution for this in forum, but could not... In my case,
When user creates a shipment using VT01N/VT02N and clicks the planning button and then clicks on save button, I need a custom idoc to be sent to SAP PI.
I tested sending this idoc from WE19 to PI and it is working fine...
But the output type is not triggering from VT01N/VT02N. I am not sure which of the config setting is wrong. Can someone point out which setting is missing/may have issues.
Also, I did an output determination analysis and it shows me a green entry which means it chose the custom output type and related access sequence. But then why is idoc not generated. I have put a break point in the custom function module in which I populate the custom idoc segment.
Please help to fill in the gaps ...
1. I checked in NACE, under V7 - Transportation, there is my custom output type ZEDI, with partner functions set as
EDI - LS - Logical system
EDI - CR - Carrier
I am not sure if this is correct !!
Processing routine points to RSNASTED, EDI_PROCESSING.
I checked the condition records tab...
The shipment type ZOUT is configured there, with one entry
ZOUT - DESCP - LS - logical system name i.e. PI system name - medium as 6.Date/Time as 3.
Again I am not sure if this is failing !!
Procedure tab does not have any entry related to this.
Access sequence also does not have any entry.
The partner profile (WE20) entries as as follows;
for the PI partner, Partner role is LS, message type is SHPMNT, under outbound params.When I double click that I see receiver port set, basic type has custo idoc name, Message control tab has V7 - ZEDI - process code ZSSS. And that process code is bound to the custom function module where I fill the idoc segment.
But finally I do not see any idoc generated !!
Please advise.

Hi ,
1. Does the condition record is automatically pulling up in the Vt02n transaction or no ?
2. Try first checking the IDOC trigger with the Standard Process Code SD11 to see if the Output Determination is working correct. Once u know that part then the partner profile setup to check with the Process Code ZSSS, whether the output is being determined or not. Based on the same atleast u can narrow down the root cause.
Are u working on this Interface for a Advance Shipment notification to the customer ?
Cheers
Balaji

Output not triggered....

Hi, I tried to find solution for this in forum, but could not... In my case,
When user creates a shipment using VT01N/VT02N and clicks the planning button and then clicks on save button, I need a custom idoc to be sent to SAP PI.
I tested sending this idoc from WE19 to PI and it is working fine...
But the output type is not triggering from VT01N/VT02N. I am not sure which of the config setting is wrong. Can someone point out which setting is missing/may have issues.
Also, I did an output determination analysis and it shows me a green entry which means it chose the custom output type and related access sequence. But then why is idoc not generated. I have put a break point in the custom function module in which I populate the custom idoc segment.
Please help to fill in the gaps ...
1. I checked in NACE, under V7 - Transportation, there is my custom output type ZEDI, with partner functions set as
EDI - LS - Logical system
EDI - CR - Carrier
I am not sure if this is correct !!
Processing routine points to RSNASTED, EDI_PROCESSING.
I checked the condition records tab...
The shipment type ZOUT is configured there, with one entry
ZOUT - DESCP - LS - logical system name i.e. PI system name - medium as 6.Date/Time as 3.
Again I am not sure if this is failing !!
Procedure tab does not have any entry related to this.
Access sequence also does not have any entry.
The partner profile (WE20) entries as as follows;
for the PI partner, Partner role is LS, message type is SHPMNT, under outbound params.When I double click that I see receiver port set, basic type has custo idoc name, Message control tab has V7 - ZEDI - process code ZSSS. And that process code is bound to the custom function module where I fill the idoc segment.
But finally I do not see any idoc generated !!
Please advise.

posted this question in ERP forum.

EDI Output not proposed in purchase order

Hi,
Trying to setup an EDI output to the purchase order and the new output is not appearing in the purchase order automatically. Strange thing is the output analysis shows the condition record is found and says "An output proposal created" ! The output appears in the drop down list, able to select it manually and create an idoc.
Did the following steps, but still missing some thing. Please help.
- Created new EDI condition type and assigned std SAP EDI processing routine.
- Assigned output type to PO output schema with manual only unchecked.
- Maintained condition record in MN05.
- Access sequence and access are fine.
Thanks in advance.
Regards,
Krishna.

Hi
Please create the condition record using MN04, instead of MN05
Thanks & regards
kishore

Condition dependent output not triggering

Hi,
We created a new PO action definition. Processing time is 4 Processing when saving document. The processing time not permitted is 00XX0 Selection report. The schedule automatically flag is checked. In the action determination section, the determination technology is set at "Determination using conditions that can be transported" and the rule type is set at "Workflow conditions". This action definition has one processing type "Smart forms print".
A condition dependent output is configured for the action definition indicated above. This condition has the default settings from action definition checked. In the processing detail tab we have a specific printer we want to use. In the schedule condition this is what I configured:
( " --- Vendor medium ---
     &EC Purchase Order.Sending Medium& = PRN
) " --- Vendor medium ---
and    ( " --- OA address number ---
     &EC Purchase Order.Vendor Address.Address Number& = 12642
) " --- OA address number ---
We have a vendor with additional ordering addresses. I got the additional address number from table BUT020. Vendor has medium "PRN" in table BBP_SENDMEDIUM.
When I create PO using the vendor and selecting the additional address (# 12642), the immediate output to the specified printer is not triggered. I mean the condition dependet output configured is not being triggered.
Please, can anyone give me some tips about what I am doing wrong.
Thanks and regards, Jose Oyon.

Hi, If you want to work with Condition-Dependent PO Output, you have
to set the conditions for output in Define action for Purchase order
output. Under Action determination and Action summarization you can
choose from different option. Also clean-up customizing inconsistencies using transaction SPPFCADM and adjust to determination technology "Determination Using Conditions" to retest. Check note 564826 which may be helpful.
Best Regards
Lauren

Message type EDI is not triggering for outbound deliveries

Hello,
When ever the shipment status is completed message type EDI is triggered for the outbound delivery.
However, in spite of the shipment completion the DESADV EDI message is not created in the outbound delivery.
So, i request you to help me in this issue.
Regards,
Anil

Hi,
1st please check the partner porfile for whom it is sent ( Eg -- Ship to party) using T.code WE20 in partner type ku, look for the customer for whom it is sent.
Check for the message type wheter it is add in outbound parameteres.
Finally check the varaint of shipment whether the required output is maintained in the shipment varaint and also make sure that condition record is maintained for the output.
You find some solution with this.
Regards
vk

PO output not triggering

Hi ,
I have created a Purchase Order and the Output type is not getting triggered.
The Condition record is maintained for document type and partner role with PArtner value field left blank.
The Partner role is not there in PO, so the output type is not getting triggered.
I enterd manually partner role in Header of PO, PArtners tab.then output was triggerd,
So, the output is looking for partner role.
So, to avoid manually etering everytime in PO, how the solution can be approcahed.
Please help

First check is there more then one Key combination.
Go in PO> Message->select the output line item--->Goto --> Determine analysis (Here you could find out which condition record is pulling automatically)
Use only one key combination for your desire output.
Please go through table B027 will help little to extract the list.

Output not triggered during SAVE from Shipment

Hi,
We have a custom Idoc triggering from the Shipment. The output shows up in the output screen (as yellow) and it is set to trigger 'immediate - 4'. But when I save, it does not issue an output. No errors, nothing just does not trigger at all. If I go into the shipment again in change mode and then save it, then it triggers the output.
The output is an custom idoc, transmission medium 6, attached program RSNASTED and the form routine is EDI_PROCESSING.
I tried debugging the program (in update debug mode)...found that an internal variable XNAST-UPDAT is set to 'D' (a GERMAN comment in code says "no longer found or changed key"). The only key change I can think of is the shipment number initially with $0001 and then changes to the actual shipment #. But this should happen even for other outputs..for eg, BoL printout. It does trigger without a problem and for this this indicator is not set to 'D'.
Any thoughts ?
Regards,
Anand

Hi Anand,
Have u resolved this issue... bcoz i m facing the same issue..
Can u plz tell me how u resolved it..
Regards,
Siva Kumar S.

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.

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

QM Block not triggered via EDI orders

Hello All,
Please help me with this problem "QM block not triggered via EDI Orders".
Sales Orders will be created using IDOC. When the sales orders was displayed using VA02, goto >> items >> schedule lines, there's no QM status violated being displayed in the delivery block column.
Kindly help me what logic will I applied regarding this matter.
FM used was IDOC_INPUT_ORDERS.
I need your comments/suggestions ASAP.
Thanks in advance.
Carina

hai,
Just check this it may help tou.
Program Name : YX30_UPLOAD_QUALITY_INFO
Quality Info Record for I30 System *
Original Transport Number : I30K903055 *
SYS id: SYS_30_1502_03_41_Upload Quality Info Records *
TDS id: TD_30_1502_03_41_Upload Quality Info Records *
UT ID: UT_30_1502_03_41_Upload Quality Info Records *
======================================================================
Change History *
Date | Change No | Name | Description *
yyyy/mm/dd | AAAYYYYMMDD | xxxxxxxxxxxx | *
REPORT YX30_UPLOAD_QUALITY_INFO MESSAGE-ID yx30_conversions
no standard page heading line-size 255.
include yx30_upload_quality_info_top. "Include for Variable Declaration & Selection Screen
include yx30_upload_quality_info_data. "Include for File read & Authority Check
*& At Selection Screen Output *
AT SELECTION-SCREEN OUTPUT. "PBO
PERFORM fill_parameters.
*& Start Of Selection Event *
start-of-selection.
Perform Authority_check. "Subroutine for authority check
Perform prepare_file. "Subroutine for preparing file
perform file_read. "Subroutine for File read
perform update_qi01. "Subroutine for Uploading data
perform write_error_log1. "Subroutine for writing error log
*& Form write_error_log
text
--> p1 text
<-- p2 text
*& Include YX30_UPLOAD_QUALITY_INFO_TOP
Type Declaration
Types: Begin of type_qtyinf,
matnr type matnr, "Material No
lieferant type char10, "Vendor
werk type werks_d, "Plant
frei_dat type char10, "Frei_Dat
stsma type char8, "Stsma
anwso_01 type char1, "ANWSO(01)
anwso_02 type char1, "ANWSO(02)
anwso_03 type char1, "ANWSO(03)
end of type_qtyinf.
Internal Table Declaration
Data: itab_qtyinf type standard table of type_qtyinf. "Internal table for QTYINF.
Work Area Declaration
Data: wa_qtyinf type type_qtyinf. "Work Area for QTYINF.
Variable Declaration
Data: v_file_qtyinf type string, "Source File Name
v1 type string,
v2 type string,
v3 type string,
v_file_return type string,
v_lin TYPE n.
*Selection Screen Declaration
selection-screen *
SELECTION-SCREEN BEGIN OF BLOCK blk1
WITH FRAME TITLE text-s01.
PARAMETER:
p_sysid(3) TYPE c OBLIGATORY , "Source System
p_bukrs(4) TYPE c OBLIGATORY , "Source CompCode
p_samshr type char30 lower case obligatory default '/sap_upload/' , "Samba Share Drive
p_object TYPE CHAR10 OBLIGATORY default 'MAT' . "Migration Data Object
SELECTION-SCREEN END OF BLOCK blk1.
SELECTION-SCREEN SKIP 3.
PARAMETER:
cb_pfill TYPE c AS CHECKBOX DEFAULT 'X' . "Prefill values?
SELECTION-SCREEN COMMENT /1(79) text-s1a.
SELECTION-SCREEN BEGIN OF BLOCK blk3
WITH FRAME TITLE text-s03.
PARAMETER:
pa_filn1(500) TYPE c LOWER CASE
VISIBLE LENGTH 50 , "Filename AppServer
pa_dlimt TYPE c DEFAULT ';' . "Field Delimter
SELECTION-SCREEN END OF BLOCK blk3.
include bdcrecx1. "Include for the subroutine
*& Include YX30_UPLOAD_QUALITY_INFO_DATA
*& Form file_read
Subroutine for reading the source file into internal table
--> p1 text
<-- p2 text
FORM file_read .
DATA:
single_line TYPE string .
*-- read file, split lines into fields and put data into table
OPEN DATASET v_file_qtyinf FOR INPUT IN TEXT MODE ENCODING NON-UNICODE. "Opening the files
IF sy-subrc EQ 0.
DO.
READ DATASET v_file_qtyinf INTO single_line. "Reading the content of file into line
IF sy-subrc = 0.
IF sy-index > 1. "skip header-line
SPLIT "Split the content of line into work area
single_line
AT ';'
INTO
wa_qtyinf-matnr "Material No
wa_qtyinf-lieferant "Vendor
wa_qtyinf-werk "Plant
wa_qtyinf-frei_dat "Frei Date
wa_qtyinf-stsma "STSMA
wa_qtyinf-anwso_01 "ANWSO_01
wa_qtyinf-anwso_02 "ANWSO_02
wa_qtyinf-anwso_03. "ANWSO_03
APPEND wa_qtyinf TO itab_qtyinf. "Appending Work Area to internal table
ENDIF.
ELSE.
EXIT.
ENDIF.
ENDDO.
CLOSE DATASET v_file_qtyinf. "Closing the files
ELSE.
MESSAGE e015 .
ENDIF.
DESCRIBE TABLE itab_qtyinf LINES v_lin.
IF v_lin LT 0.
MESSAGE e016 .
ENDIF.
ENDFORM. " file_read
*& Form fill_parameters
Subroutine for getting the file name
FORM fill_parameters .
IF cb_pfill = 'X'.
Preparing QTYINF File
CONCATENATE p_sysid '_forward' INTO v3.
CONCATENATE p_sysid '_QTYINF_' p_bukrs '.CSV' INTO v2.
CONCATENATE p_samshr v3 '/' p_object '/' v2 INTO pa_filn1.
ENDIF.
ENDFORM. " fill_parameters
*& Form Authority_check
Authority Check
--> p1 text
<-- p2 text
FORM authority_check .
Authority Check For the Migration
AUTHORITY-CHECK OBJECT 'YX30_MIGR'
ID 'SYSTEM' FIELD p_sysid
ID 'BUKRS' FIELD p_bukrs
ID 'YX30_DMOBJ' FIELD p_object
ID 'ACTVT' FIELD '16'.
IF sy-subrc <> 0.
MESSAGE e010 WITH p_sysid p_bukrs p_object.
ENDIF.
ENDFORM. " Authority_check
*& Form prepare_file
text
--> p1 text
<-- p2 text
FORM prepare_file .
CONCATENATE p_sysid '_forward' INTO v3.
CONCATENATE p_sysid '_QTYINF_' p_bukrs '.CSV' INTO v2.
CONCATENATE p_samshr v3 '/' p_object '/' v2 INTO v_file_qtyinf.
CLEAR v3.
CLEAR v2.
Prepare Return File
CONCATENATE p_sysid '_forward' INTO v3.
CONCATENATE p_sysid '_RETRUN_LOG_' p_bukrs '.CSV' INTO v2.
CONCATENATE '/sap_upload/' v3 '/' 'MAT' '/' v2 INTO v_file_return.
ENDFORM. " prepare_file
*& Form update_qi01
text
FORM update_qi01.
PERFORM open_group. "Opening a session
CLEAR wa_qtyinf.
LOOP AT itab_qtyinf INTO wa_qtyinf.
PERFORM bdc_dynpro USING 'SAPMQBAA' '0100'. "Subroutine for mapping data
PERFORM bdc_field USING 'BDC_CURSOR'
'QINF-MATNR'.
PERFORM bdc_field USING 'BDC_OKCODE'
'/00'.
PERFORM bdc_field USING 'QINF-MATNR'
wa_qtyinf-matnr. "Mapping the material
PERFORM bdc_field USING 'QINF-LIEFERANT'
wa_qtyinf-lieferant. "Mapping the vendor
PERFORM bdc_field USING 'QINF-WERK'
wa_qtyinf-werk. "Mapping the plant
PERFORM bdc_dynpro USING 'SAPMQBAA' '0101'.
PERFORM bdc_field USING 'BDC_OKCODE'
'=STAN'.
PERFORM bdc_field USING 'QINF-FREI_DAT'
wa_qtyinf-frei_dat.
PERFORM bdc_field USING 'BDC_CURSOR'
'QINF-STSMA'.
PERFORM bdc_field USING 'QINF-STSMA'
wa_qtyinf-stsma. "Mapping the status
PERFORM bdc_dynpro USING 'SAPLBSVA' '0201'.
PERFORM bdc_field USING 'BDC_CURSOR'
'J_STMAINT-ANWSO(01)'.
PERFORM bdc_field USING 'BDC_OKCODE'
'=OKAY'.
IF wa_qtyinf-anwso_01 = 'X'.
PERFORM bdc_field USING 'J_STMAINT-ANWSO(01)'
wa_qtyinf-anwso_01. "Mapping the anwso(01)
ELSEIF wa_qtyinf-anwso_02 = 'X'.
PERFORM bdc_field USING 'J_STMAINT-ANWSO(02)'
wa_qtyinf-anwso_02. "Mapping the anwso(02)
ELSEIF wa_qtyinf-anwso_03 = 'X'.
PERFORM bdc_field USING 'J_STMAINT-ANWSO(03)'
wa_qtyinf-anwso_03. "Mapping the anwso(03)
ELSEIF wa_qtyinf-anwso_01 = 'X' AND wa_qtyinf-anwso_02 = 'X'.
PERFORM bdc_field USING 'J_STMAINT-ANWSO(01)'
wa_qtyinf-anwso_01.
PERFORM bdc_field USING 'J_STMAINT-ANWSO(02)'
wa_qtyinf-anwso_02.
ELSEIF wa_qtyinf-anwso_01 = 'X' AND wa_qtyinf-anwso_03 = 'X'.
PERFORM bdc_field USING 'J_STMAINT-ANWSO(01)'
wa_qtyinf-anwso_01.
PERFORM bdc_field USING 'J_STMAINT-ANWSO(03)'
wa_qtyinf-anwso_03.
ELSEIF wa_qtyinf-anwso_02 = 'X' AND wa_qtyinf-anwso_03 = 'X'.
PERFORM bdc_field USING 'J_STMAINT-ANWSO(02)'
wa_qtyinf-anwso_02.
PERFORM bdc_field USING 'J_STMAINT-ANWSO(03)'
wa_qtyinf-anwso_03.
ELSEIF wa_qtyinf-anwso_01 = 'X' AND wa_qtyinf-anwso_02 = 'X' AND wa_qtyinf-anwso_03 = 'X'.
PERFORM bdc_field USING 'J_STMAINT-ANWSO(01)'
wa_qtyinf-anwso_01.
PERFORM bdc_field USING 'J_STMAINT-ANWSO(02)'
wa_qtyinf-anwso_02.
PERFORM bdc_field USING 'J_STMAINT-ANWSO(03)'
wa_qtyinf-anwso_03.
ENDIF.
PERFORM bdc_dynpro USING 'SAPMQBAA' '0101'.
PERFORM bdc_field USING 'BDC_CURSOR'
'QINF-FREI_DAT'.
PERFORM bdc_field USING 'BDC_OKCODE'
'=QMBU'.
PERFORM bdc_field USING 'QINF-FREI_DAT'
wa_qtyinf-frei_dat.
PERFORM bdc_field USING 'QINF-STSMA'
wa_qtyinf-stsma.
PERFORM bdc_transaction USING 'QI01'.
ENDLOOP.
PERFORM close_group. "Closing the session
ENDFORM. "update_qi01
*& Form write_error_log
text
--> p1 text
<-- p2 text
FORM write_error_log1 .
DATA:
single_line TYPE string,
v_msg TYPE string,
v_msg1 TYPE string.
*-- read file, split lines into fields and put data into table
OPEN DATASET v_file_return FOR INPUT IN TEXT MODE ENCODING NON-UNICODE. "Opening the files
IF sy-subrc EQ 0.
CONCATENATE text-020 v_lin INTO v_msg SEPARATED BY space.
CONCATENATE text-021 v_lin INTO v_msg1 SEPARATED BY space.
TRANSFER: v_msg TO v_file_return.
TRANSFER: v_msg1 TO v_file_return.
WRITE:/ v_msg.
WRITE:/ v_msg1.
ENDIF.
ENDFORM. " write_error_log
with regards.
sowjanya.b.

Delivery Output type newly created not triggering

Hi,
I have created 2 new output types i;e 1 for returns Order and one when we save the Delivery order. This i have copied the standard output type (BA00 & LD00).
so now in returns order the output type i want to trigger automatically and print. But it is not happening. In VV11 i have defined for this condition as Print immediately and in customizing also i have maintained for sales organisation. But it is NOT triggering automatically when i save the return order. If i manually go and add this output then its working. So can you please tell me what needs to be done to trigger automatically.
Secondly for Delivery i have 2 output i;e when i save the delivery without picking and all in VL01N, it should trigger 1 output and second is when i do the picking and PGI in VL02N. Both should trigger automatically.Now both my output is triggered only when i do PGI in VL02n i;e VL01N output is not triggered.
Please help how can i do that.

Hi,
Go to T-code NACE
Application area : V2-Shipping
Now select the condition records and select your new output types.
Take the key combination defined by you Viz. Sales org/Delivery Type (for example
Enter Medium as '1'
Date/Time as '4'
Press the communication Tab and Tick Print immediatley and release after output Check Box.
Also maintain the output device as LOCL
I hope this will help you
Br,
Tushar

Output Type is not triggering

Hi,
We have created routine in output determination(VOFM) to trigger the output type (for IDoc) when ever Sales Order is created and we have configured correctly. Access Sequence containes KOMKBV1, KOMPBV1, etc.
When I checked in development system, I am getting values in KOMKBV1, KOMPBV1, etc and it is serving my purpose,
But when i tested same in quality system, KOMPBV1 structure is not getting values and this is not serving my purpose ( i.e output type is not triggering) .
Could any one please suggest me why it is happening.
Regards,
Aditya.

There is no problem with Access sequence
Below are the fields for the accesss sequence.
Sales document type KOMKBV1     AUART
Sales organization      KOMKBV1     VKORG
Distribution channel     KOMKBV1     VTWEG
Division                        KOMKBV1     SPART
Customer group 5        KOMKBV1     KVGR5
Plant                             KOMPBV1     WERKS
The same is working fine in Developemnt but not in quality.
I went to debugging mode while creating a sales order in both systems for checking where exactly KOMPBV1 is getting cleared.
I could find in
SAPMV45A
MV45AF0B_BELEG_BEARBEITEN_ENDE
FORM BELEG_BEARBEITEN_ENDE
Call function messaging
When the program is going in this..... the value for KOMPBV1 is getting cleared in Quality but the same this is working fine in Development...
Hope this coulld help you in understanding the problem better.
Edited by: Aditya K Ghanaria on Nov 30, 2010 4:13 PM

Custom output type is not triggering automatically

Hi Experts,
We have created a custom output type for Delivery idoc processing.
it is working fine for all ship to patrys.
but from last 2 months onwards we are facing problem for one ship to party.
output type is not triggering automatically but for rest of ship to party's it is triggering automatically.
we have maintained conditions and also selected trigger immediately.
earlier it was working fine, but from last 2 months onwards we are facing this problem.
Thanks
Sai

Hi,
Goto the Delivery document and in the Output screen check the Determine analysis for output.
There it will clearly show what is missing .
Please check that and revert back if you need more clarification.
regards,
santosh

EDI Output not triggerring

Similar Messages

Maybe you are looking for