Check medium in output control requirement

Hello,
I have to check the medium (fax, email) in a requirement RV61BXXX (output control).
So when the medium is fax or email and some other checks are fullfilled, the output doesn't have to be processed.
When I debug this requirement I cann't find any field with the correct medium value. Isn't there any possibility to get the medium value with function modules or anything else?
As I can see, SAP gets the medium after the requirements have been processed.
Thanks,
Christine De Jaeger

HI,
If you chose other options, the driver program that you configure the SPRO or NACE, will get triggered.
In the driver program, logic must be written in order information is processed (It can be sent as Telex, Mail, Fax based on the SCOT settings and SAP Connect settings).
If the option you chose is Special function, the driver program may or may not send any mail/fax but you can do any processing . For example, if you want to update a Z Table on issuing the output, you can have that logicn in the Z program and have that attached to the output type in NACE transaction.
REgards,
Ravi

Similar Messages

VOFM formula on output control based on item category(PSTYV)

Hi Gurus,
I created an Output Control requirement in VOFM.
In the requirement ABAP codes, may I know how can I access the list of item lines category (looking for vbap-pstyv in particular) while I am creating the sales order in VA01, because the sales order is not saved yet, so I cannot get from table VBAP ?
Any way to find the variables available ?
Thanks in advance.
Best Regards,
Vasumathi
Edited by: komma vasumathi on Jun 22, 2009 3:26 PM

Hi there,
When the sales order is created, all data is stored in the internal tables 1st in USEREXIT_SAVE_DOCUMENT_PREPARE, MV45AV0V_VBAP-PSTYV_VALUES
in MV45AFZZ.
So you can refer the fields from there. Item catg is stored in XVBAP table.
But 1 doubt. Why do you want to trigger the O/p before the order is saved? Usually any O/p is triggered after saving the doc.
Once the document is saved, data is stored in data base tables & you can refer from them.
Regards,
Sivanand

Problem of configuration the requirement output control ?

Hi ,
i am now in a very urgent situation that is the system does not create the message type after executing the transaction VL31N.
In detail :
I have used the transaction NACE to configure the "Requirements output control" and i have created 3 message type (Z1 , Z2, Z3) ( type V6 : handling unit) and i have coded for each of them to check the requirements for creating the messsage type ( the message type will be created if the sy=subrc = 0 after the forms are executed.
FORM KOBEV_Z1.
Check condition from the structure komkbv6
if cond Ok
sy-subrc = 0.
endif.
ENDFORM KOBEV_Z1.
FORM KOBEV_Z2.
Check condition from the structure komkbv6
if cond Ok
sy-subrc = 0.
endif.
ENDFORM KOBEV_Z2.
FORM KOBEV_Z3.
Check condition from the structure komkbv6
if cond Ok
sy-subrc = 0.
endif.
ENDFORM KOBEV_Z3.
But in fact , even if i have put the sy-subrc = 0 for each of them or for all , the message type was not created as i need .
Result :
if the message type is created automatically after executing the KOBEV or KOBEV , a printing program will be called to print the SAPscript form , but till now , i can not do that , to print the form i have to created the message type by hand ..
Is the something wrong in the system ? How can i configure them to run well ?
Please help me .
PS : I will reward immediately and i am waiting
Thank you very much

Hi,
If you are supposed to bring across characteristic values to your target, then you will not be able to jump from the result line. The configuration expects that the values of the characteristic marked as being used in the jump are filled with unique values. When you use the result line as a source for your jump, the values in the result line will most likely be based on the sum of multiple characteristic values.
Hth,
-Jacob

How to configure the requirements for output control ?

Hi ,
I have some problems in configuring the requirements for output control like following :
My aim is to make a condition check when i create an inbound delivery ( VL31N) or MIGO ...., as default in the requirement check for output , a message type will be created automatically if the it satisfies the condition in the KOBEV .....KOBEV( each sub routine was defined with a message type ( V6 ) ( if sy-subrc = 0) . And then a printing program will be triggered to print the SAPscripts form in the table "tnapr" but even if i have put sy-subrc in ( KOBEV...KOBEV ) always = 0 the printing was not executed , and in this case i do not understand the reason why , If you please to help me this .
Thanks ,

Hi,
it seems that the requirement you made is not the reason why it's not printed. If you set sy-subrc to 0, this code should have no effect.
Cheers,
Stefan.

Print via Output Control(XNAPR) field in MIGO to be checked through BAPI

Hi Sir,
I am creating goods movement using BAPI 'BAPI_GOODSMVT_CREATE'. I am able to fill all field exect the check bos for Print via Output Control(XNAPR) field in MIGO Header screen. I am unable to find out any field corresponding to this in the BAPI structure so that I can put 'X' in that.
Please help me and I have to do this only using this BAPI.
Regards
Krishan

Hi,
I figured this one out, it's faily simple.
Within the BAPI the table USR05 is checked for Parameter ID NDR(Print via output control in MM - Inventory management) it's the parameter ID linked to the field XNAPR.
To make it work just update the table USR05 with the required setting and then execute the BAPI.
Once the procecssing is done reset the value in the table to the default.
Geting and setting the parameter ID doesn't work.
This the code I have:
Store current value in temp variable
      SELECT SINGLE * FROM usr05 WHERE bname = sy-uname
                                 AND   parid = 'NDR'.
      old_prflag = usr05-parva.
Set the new value
      usr05-parva = rm07m-xnapr.
      UPDATE usr05 SET parva = usr05-parva
                WHERE bname = sy-uname
                  AND parid = 'NDR'.
Execute the BAPI
      CALL FUNCTION 'BAPI_GOODSMVT_CREATE'
        EXPORTING
          goodsmvt_header = gm_head
          goodsmvt_code    = gm_code
          testrun          = ' '
        IMPORTING
          materialdocument = g_mblnr
          matdocumentyear = g_year
        TABLES
          goodsmvt_item    = gt_item
          return           = gt_return
          extensionin      = gt_ext.
Set the print Parameter back
      usr05-parva = old_prflag.
      UPDATE usr05 SET parva = usr05-parva
                WHERE bname = sy-uname
                  AND parid = 'NDR'.
Regards,
Jeroen

Access sequence requirement for output control

Hi!
I would like to get some inputs on how access requirement for output control works. I created a new requirement for a condition table that has key combination billing type/sales org/country because I need to restrict the output for a paticular customer in one country. I think the requirement works fine such that it is not fulfilled for the customer that I want ot restrict, thus no output is created. However, I noticed that other customers in that sales org/country are affected by the requirement. The output is created (sy-subrc=0) but it is not processed (remains in yellow status). The output should be emailed immediately upon creation (medium 5/timing 4). For other sales org/countries the creation of output and sending of email work as expected.
I hope someone have valuable inputs regarding this.
Note: I created this discussion under ABAP development but it was rejected, for reason: This does not appear to be an ABAP question. So I hope I have selected the correct one with SD.
Cholen

There is Output determination log available in the output screen (see the menu). It tells everything about how the output was proposed.
If the requirement is not fulfilled, you won't see output created with any color - yellow, red or purple with sparkles. If output has been proposed and has a yellow light it means it has not been processed yet. Output is processed only after the document has been saved, so while creating the document, you'll never see any other color. If after saving the document output is still yellow, it must have a different timing than 'process immediately' and it will be processed according to that setting.
This is a very simple concept, well documented and discussed gazillion of times on SCN. Requirements and conditions are two different things with different purposes. You might want to read a bit more on the output determination.
Thank you.

VOFM(Requirements Output Control)

Hi all,
We have custom output type configured which has to be displayed alone when a invoice is created for particular customer....All this part is done...but now i need to create a form routine and a requirement which wud be assigned to this output type which would display only this output type(Zxyz) say and should'nt display other standard output types like RD01 and other output types in the invoice outptut messages.....
How to create a routine is my first question for output control.
How to right a code in the routine which wud have only ZXYZ output type in the output message for particular Invoices.....

Hi,
Create a routine and assign the VOFM routine to all the other output types in the procedure except for the new one..
You can create the routine in the transaction VOFM..
In the VOFM routine have this logic.
If KOMKBV3-kunag = 'my specific customer'.
sy-subrc = 4.
ELSE.
sy-subrc = 0.
ENDIF.
Hope this helps..
Thanks
Naren

How to display check box in atable control

hi
here is my requirement
how can i display check box in table control and also when i check that check box it has to dispaly one pop up screen with the records of table control row
points will be rewarded
Thanks&Regards
Nagesh.Paruchuri

Hi,
See this code for how to display check box in atable control
*---- Table declaration.
TABLES: KNA1.
CONTROLS TC1 TYPE TABLEVIEW USING SCREEN 200.
CONTROLS TC2 TYPE TABLEVIEW USING SCREEN 300.
*---- Data declaration.
DATA:OKCODE LIKE SY-UCOMM.
DATA:V_KNA1 LIKE KNA1.
*DATA:ERROR TYPE C.
*---- Internal Table declaration.
DATA:BEGIN OF IT_TAB OCCURS 0,
      CHK,
      VBELN TYPE VBELN_VA,
      KUNNR TYPE KUNAG,
      ERDAT TYPE ERDAT,
      AUDAT TYPE AUDAT,
      VBTYP TYPE VBTYP,
     END OF IT_TAB.
DATA:BEGIN OF IT_TAB1 OCCURS 0,
      VBELN TYPE VBELN_VA,
      POSNR TYPE POSNR_VA,
      MATNR TYPE MATNR,
      MATWA TYPE MATWA,
      PMATN TYPE PMATN,
     END OF IT_TAB1.
*&      Module USER_COMMAND_0100 INPUT
MODULE USER_COMMAND_0100 INPUT.
OKCODE = SY-UCOMM.
CASE OKCODE.
    WHEN 'DISP' OR SPACE.
      SELECT *
         FROM VBAK
         INTO CORRESPONDING FIELDS OF TABLE IT_TAB
         WHERE KUNNR = KNA1-KUNNR.
      IF SY-SUBRC <> 0.
        MESSAGE 'No sales document exists'(001) TYPE 'I'.
      ENDIF.
      LEAVE TO SCREEN 200.
      CLEAR OKCODE.
*--- To leave Transaction
    WHEN 'BACK' .
      LEAVE PROGRAM.
      CLEAR OKCODE.
ENDCASE.
ENDMODULE.                 " USER_COMMAND_0100 INPUT
*&      Module validate_kunnr INPUT
MODULE VALIDATE_KUNNR INPUT.
V_KNA1 = KNA1.
SELECT SINGLE *
    FROM KNA1
   WHERE KUNNR = KNA1-KUNNR.
*-----Process error condition
IF SY-SUBRC <> 0.
    CLEAR KNA1.
    KNA1-KUNNR = V_KNA1-KUNNR.
    CASE OKCODE..
      WHEN 'BACK' OR 'EXIT' .
        LEAVE PROGRAM.
    ENDCASE.
    MESSAGE 'Customer Does Not Exist'(002) TYPE 'I'.
    LEAVE TO SCREEN 100.
ENDIF.
ENDMODULE.                 " validate_kunnr INPUT
*&      Module STATUS_0100 OUTPUT
MODULE STATUS_0100 OUTPUT.
SET PF-STATUS 'PF'.
ENDMODULE.                 " STATUS_0100 OUTPUT
*&      Module USER_COMMAND_0200 INPUT
MODULE USER_COMMAND_0200 INPUT.
CASE OKCODE.
    WHEN 'BACK' OR 'EXIT' OR 'CANCEL'.
      LEAVE TO SCREEN 100.
      CLEAR OKCODE.
      CLEAR IT_TAB1.
    WHEN 'DISP' .
      CLEAR OKCODE.
      READ TABLE IT_TAB WITH KEY CHK = 'X'.
   IF SY-SUBRC = 0.
        SELECT VBELN   POSNR MATNR MATWA PMATN
     FROM VBAP
     INTO TABLE IT_TAB1
     WHERE VBELN = IT_TAB-VBELN.
        IF SY-SUBRC = 0.
          SORT IT_TAB.
          DESCRIBE TABLE IT_TAB LINES TC1-LINES.
          LEAVE TO SCREEN 300.
        ELSE.
          MESSAGE E016(YBHV).
        ENDIF.
      ELSE.
        MESSAGE 'Please select one record' TYPE 'I'.
      ENDIF.
ENDCASE.
ENDMODULE.                 " USER_COMMAND_0200 INPUT
*&      Module STATUS_0200 OUTPUT
MODULE STATUS_0200 OUTPUT.
SET PF-STATUS 'PF3'.
ENDMODULE.                 " STATUS_0200 OUTPUT
*&      Module USER_C.OMMAND_0300 INPUT
      text
MODULE USER_COMMAND_0300 INPUT.
SET PF-STATUS 'PF3'.
CASE OKCODE.
    WHEN 'BACK' OR 'EXIT' OR 'CANCEL'.
      CLEAR OKCODE.
      LEAVE TO SCREEN 200.
ENDCASE.
ENDMODULE.                 " USER_COMMAND_0300 INPUT
*&      Module modify INPUT
MODULE MODIFY INPUT.
MODIFY IT_TAB INDEX TC1-CURRENT_LINE.
ENDMODULE.                 " modify INPUT
*&      Module okcode OUTPUT
      text
MODULE OKCODE OUTPUT.
CLEAR OKCODE.
ENDMODULE.                 " okcode OUTPUT
Reward Pointsa If usefull
Regards
Fareedas

Output Control Routine for Order Confirmation

Hi,
I have a problem in sending out order confirmation when the customer have a credit block, no order confirmation is being sent.
Checked on transaction NACE, the routine for Order Confirmation (Routine 2), returns a sy-subrc =4
when the credit block is set. What is the best way to correct this?
Thanks,
Catherine

Create the new routine in VOFM->Requirement->Output Control. Make the required changes in routine source text and assign it to output procedure (NACE).
Thank You,
Ganesh

PO Output control

Hello,
I am trying to define a requirement such that a new output for a PO is through medium EDI, and any repeat (or change) output are assigned medium Fax as default.
Request you to help me resolve it.
Thanks
Rajeev

Hi,
Please take a look at the following links,they contain the details requested related to PO Output control.
http://help.sap.com/saphelp_nw04/helpdata/en/dc/6b7c9f43d711d1893e0000e8323c4f/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/69/e5cb365f6511d2b458006094b9476a/content.htm
<b>Reward if helpful.</b>
How to reward?
Click on the star icon next to the response for which you wish to reward points. A popup window will appear. Use the radio buttons to mark a response "Solved My Problem," "Very Helpful," or "Helpful."

Reg:output control

Hi i am interested to know the configuration details for maintaining output determination.Pls send me any material to my mail id.
My id is:[email protected]
Thanks&ragards

Hi Kishore Kumar,
OUTPUT DETERMINATION:
Output determination in sales and distribution allows you to control proposal using assignments and groupings in such a way that the system selects the output allowed in each sales transaction and carries out output processing according to predefined criteria.
In the SAP System there are two possible ways of controlling output determination for each output:
proposal of output from the customer master record
proposal of output using the condition technique
SAP recommends the output proposal using the condition technique. This is because it is much more flexible than taking the proposal via the customer master. For example, the condition technique makes it possible to determine the most suitable output from several different types of output.
Note
Output control occurs separately in the header and item levels.
The proposal of output for sales support outputs can only be carried out using the condition technique.
Hope you are aware of that the output determination is done for
1. Sales Activities
2.Sales Documents
3.Delviery
4.Shiping and Transportation
5.Billing
FOR Customization please follow below steps:
MENU ;- IMG --> Sale and Distribution --> Basic Functions --> Output Control -->
Output Determination --> Output Determination using Condition Technique :
Maintain Output Determination for Sales Documents :
1.Maintain Condition Tables
2.Maintain Output Types
3.Maintain Access Sequence
4.Maintain Output Determination Procedure
5.Assign the Output Determination Procedure.
Finally Create condition Record using the T.Code: VV11
Then Create the Sales Order and Save it and go to the same sales order in Change mode.
Here in Sales Order main Screen --> Click on Extras --> Output --> Header --> Click on Print Preview.
T.Code: NACE
Output Determination
Output is a form of media from a business to one of its business partners. The possible media forms are printouts, faxes, telexes, e-mails, and EDI. The output can be sent to any of the partners defined in the document. Outputs are usually in the form of order confirmations, delivery notes, invoices, and shipping notifications.
Output determinationOutputBasic fncsSDIMG
An output type is simply a type of output and it contains all the control features for the output. For ex, it defines the kind of output, which business transaction it applies to, which business partner receives the output, how the output is sent (the media), and the print program and SAP Script layout to use in formatting the output.
Output determination can be maintained as originating from the customer master record or as originating by using the condition technique.
Output proposal from the customer master record
Output proposal from the customer master record, Define outputOutput determinationOutputBasic fncsSDIMG
In this option one creates output types, such as BA00 (order confirmation). After creating the output type, one assigns the output type to an output procedure, such as DB0001. After the assignment of the output types to the procedure, the output procedure is then assigned to the customer account group. This is a simple procedure and results in the output that is placed on the customer master record being copied into the sales document.
Out put determination procedure
In SAP we can send the documents to respective partner functions through different transmission mediums. SAP uses condition technique to determine output t relevant partners with relevant transmission mediums.
Out put determination procedure has a integration with technical module, as ABAPers has to write SMART forms and FORMS to print the output , that SMART form output can be send to relevant partner function through relevant transmission mediums.
Out put determination procedure for order confirmation: (V/57)
a) Maintain condition table:
Path:
IMG
SD
Basic functions
Output control
Output determination
Output determination using the condition technique
Maintain out put determination from for sales document
Maintain condition tables
Maintain out put condition table for sales document
Here we define condition table
Ex: 007 order type (sales order types)
Save it
b) Maintain output types:
IMG
SD
Basic functions
Output control
Output determination
Output determination using the condition technique
Maintain out put determination from for sales document
Maintain out put types
Here we define out put types
Ex: AF00 -- Inquiry
AN00 quotation
BA00 Order confirmation
BA01 EDI odd response
KRMLCredit processing
LP00 -- Scheduling agreement
MAIL Internal message
RD03cash sales invoice
Choose BA00 copy it and rename as a MA00
click on details icon
click on display to change icon
then again choose MA00 click on details icon
Maintain data in general data tab
General data tab:
Access sequence: 0010(order type)
In IMG define access sequence and assign to the output type
Check access to conditions:
This indicator allows the system to read the condition records for output. If it is not been activated then system determines out put from customer master ex: By following out put determination procedure DB0001
Check cannot be changed:
This control specifies whether the out put can be changed or not
Ex: direct mailings can be changed during processing
Check multiple issuing:
This indicator allows the system to send the output multiply
Ex: sales order has been sent for 10 items again one item has been added to sales order so that business has to issue the new out put for sold to party with added line items. This indicator allows the system to send out put repeatedly.
Check partner independent out put:
During output processing when the indicator has not set then system allows only specific functions in specific partner functions
Dont write processing:
This indicator determines whether system has to write processing log for output
Default values tab:
Dispatch time:
Ex: send immediately: when carry the application this indicator determines when the output should be sent.
Transmission medium:
Ex: print out
Fax
Telex
Internal send
EDI
Simple mail
Special function
Events (SAP business workflow)
Distribution (ALE)
Tasks (SAP business work flow)
Specify the transmission medium through which the output should be sent. (Ex: print output)
Communication strategy
Specify the communication strategy if you want to send the output externally
A) Time tab:
Check timing: (Periodic job not allowed)
This indicator allows the system to carry out print program periodically.
B) PRINT NEXT TAB):
Print parameter: Ex sales org.
Specify the print parameter.
Click on mail title & Text control button under dialog structure.
Here we assign title for the mail along with relevant text Ex:-EN (English)
Processing routines control button under dialog structure.
Here we assign programs form routines & form that are written by ABAPER, they they various transmission mediums.
Ex; - Transmission medium shortest program form routine
1 print out RVADOR entry
Click on position function control button here we assign relevant partner function to relevant transmission mediums
EX: print out: SP (Sold to party)
C) Maintain access sequences:
Here we define Access sequence.
EX: 0010 & Assign the condition tables to this output.
D) Assign out put types to partner function:
Here we assign output types along with transmission mediums to relevant partner functions.
EX: Out put type Transmission medium
MA00 1
2
6
A
MAIL 7
E) Maintain output determination procedure:
Here we define output determination procedure
Ex: V10000 - Order output
V05000 - Inquiry output
V06000 - quotation output
V10001 - Cash sales output
Choose output determination procedure EX; V10000, copy it& rename it as MA0000
Assign output type MA00 by going control date section.
Save it.
F) Assign output determination procedures;
Allocate sales document Header.
_ Choose sales document type OR & Assign output determination procedure i.e MA0000 & Assign output type MA00.
Assign sales document items.
-Choose item category TAN & Assign output determination procedure Ex: Ma0000
- save it & exit.
Maintain output records (vv11)
Path:
Logistic > S&D > Master data > output > sales document > VV11 Create
Specify output MA00, Click on Key combination & specify sales document type (OR), partner function (sp) transmission medium (1) dispatch type (4) language (EN)
Click on communication button on application tool bar
Specify output device LOCL or LP01
Check print immediately check release after output
Save it
Go to Va01 raise the sales order
Go to extra button output header edit.
Specify output type: MA00 partner function
Select line, click on communication methods
Specify logical destination
Check print immediately
Check release after output
go back save it & exit
Go to VA02, Go to Extras output header print preview
Check out (order confirmation )
Please Reward If Really Helpful,
Thanks and Regards,
Sateesh.Kandula

Output control in VOFM

Hi All,
I have written a routine in output control of VOFM to check the sales order type before generating the invoice.
I am not able to find the sales order number which is generated currently before creating the invoice.
I have given the Query as below....
select single vbelv from vbfa into w_vbelv
where vbeln = komkbv3-vbeln.
But komkbv3 is giving the invoice number which is going to genearte after requirement program.
I have to get sales order number there.
Could you plz anybody help me on this...
Regards,
Sekhar D

You don't have to hit standard tables to find the sales order type, try to find it out from global variables in the debugger, it might be available somewhere in the program.
Its not possible to get the document number which is being processed currently, because number will be assigned once all check and validations are over.
Regards
Karthik D

How to remove the mandatory field setting in output control

Hi everybody,
While printing a Payment Voucher through F-58 and FBZ5(reprint), there are two output devices, the first one is - printer for forms and second is - payment advice printer.
In our case we have configured the cheque printing and payment voucher printing seperately. The cheque goes to first printer(kept mandatory field) and the payment voucher goes to second printer. One of our plant does not print the cheque from SAP, they only print the payment voucher because the cheque is manually prepared. How do I avoid the cheque printing. Is there any way out to print only the payment voucher through F-58 and FBZ5
Please guide me how to tackle it or how to remove the mandatory field setting in the output control screen?
Regards
Paul

Hi
As of my understanding, there is no relation ship between the Sales Organization and this mandatory partner function.
Here are few suggestions.
1. Since Partner functions are defualted and made mandatory in the Partner Determination Procedure so you have to remove this Mandatory option for PE from the Partner Determination Procedure that is AG if using standard one.
2. If you are using a single partner function than , Copy and create a New partner procedure and a new account group . Where in one you can default PE as mandatory and in another one you make a optional where it can be choosen manually while creating the customer.
Follow the path to check for entries :
SPRO > sales & distribution > Basic Function > Partner Determination > set up partner determination > select for customer master > select the partner procedure you are using AG as standard > then partner function in procedure > here maintian the check as required like, Mandatory or No check for Non Mandatory .
Thanks
RB

How to add check box in table control?

Dear frnds,
In our requirement i am used tablec ontrol for dialog programming, but i am confused about addition of check box as fields in table control.
Any help are welcome from your side.

Hi,
Chk this demo program: DEMO_DYNPRO_TABCONT_LOOP_AT
& RSDEMO02.
Another way:
Go to the edit mode of the screen select the table control column you want to make it as check box and follow the menu EDIT->CONVERT->check box.
(make sure that column definition in itab/ddtab is of size 1 char)
Also chek out this link:
Add Check box in Table control
Hope these help you.
Regards,
Anjali

Purchase Order Output Control

Hi,
I am trying to create an ORDERS05 IDoc when a PO is created and sent to a folder via EDI processing.
Here are the steps I followed...
1. Created RFC Destination for EDI Subsystem (TCP/IP connection)
2. Created File port and included the RFC Destination in the Outbound trigger tab.
3. Created partner profile (Vendor)
         a. Outbound parameters - message type ORDERS,
                  i. Outbound Options - receiver port - file port created in step 2
                                                basic type - ORDERS05
                  ii. Message Control - Application - EF
                                                 Message Type - NEU
                                                 Process Code - ME10
4. Create PO (ME21)
when I look under Menu Header -> Messages it goes to a printer instead of the File Port I created.
Am I missing a step? Please let me know.
Thanks,
Sneha

Thanks Kalpanashri,
I followed what you said and this is what I received...
<i>Maintain outgoing EDI-connection data for partner 1002514
Message no. VN032
Diagnosis
The system could not locate the EDI partner agreements (outbound) for partner 1002514.
System response
You cannot use transmission medium 'EDI' with this partner.
Procedure
Maintain the EDI partner agreements for partner 1002514. Make sure to create entries for output control as well as for outbound parameters.</i>

Check medium in output control requirement

Similar Messages

Maybe you are looking for