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

Similar Messages

Field to MIGO cert.enclosed in the BAPI BAPI_GOODSMVT_CREATE

Hi All,
I am doing Good Receipt for Purchase Order.
In MIGO we have Cert.enclosed (Quality) value Yes or No.
I want to insert the Cert.enclosed (Quality) using BAPI BAPI_GOODSMVT_CREATE.
Please let me know which field in BAPI_GOODSMVT_CREATE, I can insert the Cert.enclosed (Quality) value.
Thanks in Advance.
Debopriya G

Please take a look at SAP KBA- 0001718791. Kindly mark if helpful.
SAP Knowledge Base Article
Symptom
There is no import parameter in BAPI_GOODSMVT_CREATE that you can use to confirm the QM certificate.
Environment
SAP Release Independent
Reproducing the Issue
1. In T-code SE37, execute the function module BAPI_GOODSMVT_CREATE
2. In the import tab and tables tab, check all the parameters, there is no place to enter the QM certificate (COA)
Cause
Missing functionality in BAPI_GOODSMVT_CREATE
Resolution
Please use BDC (batch input) for MB** transactions (MB01, MB0A, MB1A, MB1B, MB1C, etc.) instead.
Keywords
QCERT_MIGO-ANSWER, QBCK_QM_GR_CHECK
Header Data
Product
This document is not restricted to a product or product version
References
This document refers to:
CSS SAP Notes
1718791 - Certificate of Analysis (COA) in BAPI_GOODSMVT_CREATE
Version 1 Validity: 05/15/2012 - active Language English
Released On 02/12/2013 02:32:24
Release Status Released to Customer
Component MM-IM-GF-BAPI BAPIs for Goods Movements
QM-CA Quality Certificates
Priority Normal
Category How To
304122 MIGO: Batch input and CATT not supported
Other Components

Need Code For PO-GR through MiGO for multiple documents through BAPI

Hi All
Im using BAPI_GOODSMVT_CREATE to post goods for PO-GR.
When im posting multiple documents its giving error.
When im posting individually, it's working fine.
Please send me the code for PO-GR through BAPI.
Urgently required.
Regards,
SImha.

Is this not working???
BAPI_GOODSMVT_CREATE to post Goods Movement
The following is an abap program making used of the BAPI function BAPI_GOODSMVT_CREATE to do Goods Receipts for Purchase Order after importing the data from an external system.
BAPI TO Upload Inventory Data
GMCODE Table T158G - 01 - MB01 - Goods Receipts for Purchase Order
                     02 - MB31 - Goods Receipts for Prod Order
                     03 - MB1A - Goods Issue
                     04 - MB1B - Transfer Posting
                     05 - MB1C - Enter Other Goods Receipt
                     06 - MB11
Domain: KZBEW - Movement Indicator
     Goods movement w/o reference
B - Goods movement for purchase order
F - Goods movement for production order
L - Goods movement for delivery note
K - Goods movement for kanban requirement (WM - internal only)
O - Subsequent adjustment of "material-provided" consumption
W - Subsequent adjustment of proportion/product unit material
report zbapi_goodsmovement.
parameters: p-file like rlgrap-filename default
                                 'c:\sapdata\TEST.txt'.
parameters: e-file like rlgrap-filename default
                                 'c:\sapdata\gdsmvterror.txt'.
parameters: xpost like sy-datum default sy-datum.
data: begin of gmhead.
        include structure bapi2017_gm_head_01.
data: end of gmhead.
data: begin of gmcode.
        include structure bapi2017_gm_code.
data: end of gmcode.
data: begin of mthead.
        include structure bapi2017_gm_head_ret.
data: end of mthead.
data: begin of itab occurs 100.
        include structure bapi2017_gm_item_create.
data: end of itab.
data: begin of errmsg occurs 10.
        include structure bapiret2.
data: end of errmsg.
data: wmenge like iseg-menge,
      errflag.
data: begin of pcitab occurs 100,
        ext_doc(10),           "External Document Number
        mvt_type(3),           "Movement Type
        doc_date(8),           "Document Date
        post_date(8),          "Posting Date
        plant(4),              "Plant
        material(18),          "Material Number
        qty(13),               "Quantity
        recv_loc(4),           "Receiving Location
        issue_loc(4),          "Issuing Location
        pur_doc(10),           "Purchase Document No
        po_item(3),            "Purchase Document Item No
        del_no(10),            "Delivery Purchase Order Number
        del_item(3),           "Delivery Item
        prod_doc(10),          "Production Document No
        scrap_reason(10),      "Scrap Reason
        upd_sta(1),            "Update Status
      end of pcitab.
call function 'WS_UPLOAD'
exporting
    filename                      = p-file
    filetype                      = 'DAT'
IMPORTING
FILELENGTH                    =
tables
    data_tab                      = pcitab
EXCEPTIONS
FILE_OPEN_ERROR               = 1
FILE_READ_ERROR               = 2
NO_BATCH                      = 3
GUI_REFUSE_FILETRANSFER       = 4
INVALID_TYPE                  = 5
OTHERS                        = 6
if sy-subrc <> 0.
message id sy-msgid type sy-msgty number sy-msgno
          with sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
exit.
endif.
gmhead-pstng_date = sy-datum.
gmhead-doc_date = sy-datum.
gmhead-pr_uname = sy-uname.
gmcode-gm_code = '01'.   "01 - MB01 - Goods Receipts for Purchase Order
loop at pcitab.
itab-move_type = pcitab-mvt_type.
itab-mvt_ind    = 'B'.
itab-plant      = pcitab-plant.
itab-material   = pcitab-material.
itab-entry_qnt = pcitab-qty.
itab-move_stloc = pcitab-recv_loc.
itab-stge_loc   = pcitab-issue_loc.
itab-po_number = pcitab-pur_doc.
itab-po_item    = pcitab-po_item.
concatenate pcitab-del_no pcitab-del_item into itab-item_text.
itab-move_reas = pcitab-scrap_reason.
append itab.
endloop.
loop at itab.
write:/ itab-material, itab-plant, itab-stge_loc,
          itab-move_type, itab-entry_qnt, itab-entry_uom,
          itab-entry_uom_iso, itab-po_number, itab-po_item,
                                              pcitab-ext_doc.
endloop.
call function 'BAPI_GOODSMVT_CREATE'
exporting
    goodsmvt_header             = gmhead
    goodsmvt_code               = gmcode
TESTRUN                     = ' '
IMPORTING
    goodsmvt_headret            = mthead
MATERIALDOCUMENT            =
MATDOCUMENTYEAR             =
tables
    goodsmvt_item               = itab
GOODSMVT_SERIALNUMBER       =
    return                      = errmsg
clear errflag.
loop at errmsg.
if errmsg-type eq 'E'.
    write:/'Error in function', errmsg-message.
    errflag = 'X'.
else.
    write:/ errmsg-message.
endif.
endloop.
if errflag is initial.
commit work and wait.
if sy-subrc ne 0.
    write:/ 'Error in updating'.
    exit.
else.
    write:/ mthead-mat_doc, mthead-doc_year.
    perform upd_sta.
endif.
endif.
      FORM UPD_STA                                                  *
form upd_sta.
loop at pcitab.
    pcitab-upd_sta = 'X'.
    modify pcitab.
endloop.
call function 'WS_DOWNLOAD'
    exporting
      filename                      = p-file
      filetype                      = 'DAT'
IMPORTING
FILELENGTH                    =
    tables
      data_tab                      = pcitab
EXCEPTIONS
FILE_OPEN_ERROR               = 1
FILE_READ_ERROR               = 2
NO_BATCH                      = 3
GUI_REFUSE_FILETRANSFER       = 4
INVALID_TYPE                  = 5
OTHERS                        = 6
endform.
*--- End of Program
REgards,
Ravi

How to update Assignment field in Accounting Document through BAPI ?

I need to change Assignment field in already posted accounting document through bapi or some other automatic method. Please tell me exactly which bapi I should use and how can I pass the changed assignment field?

Hey,
I couldnt find any BAPIs which update an accounting document. I think the safest way is to record FB02 and use BDC/Call Transaction.
-Kiran
*Please reward useful answers

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

Adding XNAPR field in MIGO_GR selecting different output type

Hi,
We are setting the NDR parameter in table USR05 to set XNAPR field to 'X' in MIGO_GR transaction in our custom program through BAPI_GOODSMVT_CREATE. It is updating the field successfully in the transaction. But it is setting the output type as ZAR1 whereas if we manually post a document using MIGO_GR, the output type is selected as ZNBC.
Could you please provide me with any suggestion or solution to this problem?
Regards,
Hardeep Kaur

HI
add that fileds in the all locations where you need it like
in internal table declaration , write statement , select statement
these are the main areas where you have to add that 2 fileds

Output determination for PO and MIGO

HI,
Please provide me complete config of output determination for PO and MIGO.
PO print out.
GR, GI,TP, cancellation and return print out
Uts

Hi,
Please go through these steps you can get the GRN Printout
1. Maintain the Printer Name in SPRO->Matl Mgmt->Inv Mgmt and Phy Inv->Print Control->Gen Settings->Printer Setting
Enter the local printer where you want to print your Goods posting document
2. Ensure that in SPRO->Matl Mgmt->Inv Mgmt and Phy Inv->Print Control->Gen Settings->Item Print Indicator, 1 stands for Matl Doc print out
3. In SPRO->Matl Mgmt->Inv Mgmt and Phy Inv->Print Control->Gen Settings->Print Version, maintain Print Version 2
4. In SPRO->Matl Mgmt->Inv Mgmt and Phy Inv->Print Control->Maintain Print Indicator for Goods Receipt/GI/Transfer Posting Documents
Here for Particular mvt type 101,201,121,311 etcu2026 Maintain the Print item as 1--Material document printout
5. In SPRO->Matl Mgmt->Inv Mgmt and Phy Inv->Output Determination->Maintain Output Types, for the Output types WE01, WE02 and WE03, ensure the following--
Select the particular Output type then goto Details
a. Default Values: Dispatch Time is 3 or 4 as per reqmt. and Transmission medium is 1
b. Print Parameter is 7
6. In SPRO->Matl Mgmt->Inv Mgmt and Phy Inv->Output Determination->Printer Det->Printer Determination by Plant/Str Loc, Maintain the Output device for all your Plants
7. Go to MN21, for Tr Type WE, Print Version 3, maintain Print Item as 1.
Now the settings are ready for Printing Material doc
8. While doing MIGO, ensure that in General Tab, you get "3 Collective Slip" beside the Print Indicator and you tick mark the field.
9. Now depending on the setting in 5a, the Matl doc is printed. If it is 3, you have to print it using MB90. If it is 4, it is printed immediately.

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>

Printing problem using Dot Net - fields are drifting off specified co-ords

Hello
I am writing a crystal report that requires exact positioning of data to fit preprinted stationery.
I have achieved this satisfactorily in design mode (CR XI) and the report prints according to requirements from design mode.
I have loaded the report into our Dot Net app and printed the same report from there and the x,y cordinates of the output is slipping more and more both across and down the page.
e.g the differences vary on the x co-ord from 5mm to 13mm working left to right and 1mm to 10 mm vertically from top to bottom.
This error is evident in both preview and printing via Dot Net but is perfect in design mode.
I am using CR12 merge modules from the dot Net app.
I have tried locking fields and size and unlocking them - it makes no difference.
I hope there is a simple solution for this as I have been tearing my hair our trying to solve this problem.
Thanks in anticipation.
Richard

Using Crystal 2008, I can explain the fundemental problem that I have with the drifting of the output, even from design mode.
1) Create a brand new report.
2) In page setup, zeroise all margins.
3) On the design tab place a text box on the report with contents "XXXX" in it.
4) Format Field options - add top and left margin line
5) Duplicate the field
6) First field - right click and choose "size and position" and set to X : 15 (cm) Y : 25 (cm)
7) Second field - right click and choose "size and position" and set to X : 2 (cm) Y : 2 (cm)
8) Print the report
The boxes on the report actually print at :-
Box 1 : X 2.35 (cm), Y : 2.5 (cm)
Box 2 : X 14.7 (cm), Y : 24.4 (cm)
Now, this problem only seems to have started happening since moving up to 2008 merge modules for our Dot Net app, but this issue appears to originate in design mode too, although I have not written any of our reports in CR 12 as yet.
I really need some help with this as this could cause issues in 500 reports already written in CR XI.
I hope someone has a very simple solution for me
Regards
Richard

Restrict IDOC processing through output control

Hi,
We want to send one idoc (ORDERS) only to a particular logical system while creating purchase order through output control
Can anybody explain how we can restrict sending idoc to only one logical system?
Thanks in advance

You can control output processing for shipments(VT01n docs) based on overall status by maintaining Activity profiles for shipment types.
SPRO: Logistics execution->Transportation->Shipments->Define and assign activity profiles.
Type a variant name in the status field you want to process edi for the shipment type and click on maintain.
Select shipment checkbox in the 'Print after save' box and enter the EDI output type.
Regards
Sridhar

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

Choose Printer for Output - Condition records

Hi all,
We are maintaining condition records at inventory management, shipping,pick list & pack list.
at the time of print,can be able to choose the printer. Is that feasible? Can a condition record prompt the user to choose a printer for the output?
Can anyone help me out..

Hi,
When you maintain your condition master records, (VV11, VV21, VV31) you can maintain which printer you want to print via the button option "Communication"
Field - Output Device"
Under that field you can give exactly which printer you want to print this output.
Else what you can do is, Set this field as LOCL, which means the local printer of the user who is printing these outputs.
Then in the local machine set the required printer as default printer. (This is a Windows setting). Then when he/she try to print an output, SAP goes to the LOCAL printer and from there it find the default printer of the user machine.
You can use one of above!
Hope this helps!
Best regards,
Rahal

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.

Error during print request output. l_rc = 1

Hi ,
I have a request to create on ouput device which can copy the spool request to desired location in application server. Our server is not connected to any physical server and is windows NT.
I am tring to create ACCESS TYPE 'L' with host printer name '__default'.
I am using control set to copy file at desired location on server
COPY &F <path for file to be copied>&T
File is being copied to desired location but its returing error message "Error during print request output. l_rc = 1"
Complete log is below:
      SAP spool error log
      =====================
Print request processing log
The host spool is reporting errors
Message from host spool:
1 file(s) copied.
End of message
Command used: COPY E:\usr\sap\D06\DVEBMGS00\data\000002934300001.D06 E:\interface\D06\
Errors occurred processing this print request
Error during print request output. l_rc = 1
There may be no printout
Most important attributes of spool request
Request number 29343
Request name SCRIPT ZRAJ BASISADMIN
Client 220
Owner BASISADMIN
Request attributes
Time created   2008102906203900
Remaining life +00008000000
Dispo 1 (Go/Hold) G
Dispo 2 (Keep/Delete)     K
Dispo 3 (Indirect/Direct) D
Default output device ZRAJ
Default no. copies 1
Format X_PAPER
Main print request characteristics
Spool request number 29343
Print request number 1
Print request attributes
Time created   2008102906203900
Output device ZRAJ
Format X_PAPER
Character converter active when first problem occurred
No information available
Pls help.
Regards
Raj Kiran

If you have done a search with your subject line, you would have got the following [results.|https://www.sdn.sap.com/irj/sdn/advancedsearch?query=%22errorduringprintrequestoutput.l_rc%3D1%22&cat=sdn_all]
so do a search in SCN before posting your question.
Regards
Karthik D

Report Output for Currency Field--EKBE-WRBTR

Hello ABAP Experts
Since the Issue is related with Related Report output. Thought ABAP General Forum would be right place to post.
If not Suggest an appropriate forum for the same. I shall post them in Correct Forum.
Currently the report display Currency value From EKBE- WRBTR field
Actual Record Stored in EKBE is like this
0,00
400,00
1.600,00
client requirement is
0, 00
400,00
1600, 00
Option-1
I have tried option for conversion to CHAR & printing in Output, the issue I face is when I export to Excel I am getting an ABAP Error CONVT_NO_NUMBER(Short Dump)-This dump is due to conversion while exporting to excel.
Option-2(from SDN)
Give a logic based on T005 table i.e. this table has the decimal place setting for a each country (this I need to Verify)u2014But the I fear that report output can be confusing.
Expecting all your expert inputs!!
BR
Bharath

Hi Bharat,
You can set it using user--profile I guess.
For own data go to
system>user profile>own data---> defaults.
There you can select the currency format.
Hope this helps you.
Thanks,
Arun

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

Similar Messages

Maybe you are looking for