GR print out- collective

How do i take GR print out in a continuous pages? currently i am able to take line itm by line item only which is cumbersome as my GR docuement has 12 line items I do not want 12 documents to be printed instead it should come in 1 or 2 pages like a normal Po print out.
regards
samuel mendis

Hi,
While doing MIGO, choose 'Collective slip' at Printing tab.
This will solve your problem.
regards

Similar Messages

GR Collective slip Print out

Hi,
When user was making GR with multiple line itmes and he selected Collective print out option to print GR Note. But still only one line items get printed not all the line item. What will be the problem
Thanks in Advance

HI,
check have u maintain WE03 as output type
In SPRO->Matl Mgmt->Inv Mgmt and Phy Inv->Output Determination->Maintain Output Types, for the Output types WE01, WE02 and WE03, also ensure the foll:
a. Default Values: Dispatch Time is 3 or 4 as per reqmt. and Tr medium is 1
b. Print Parameter is 7
Then Go to MN21, for output type WE03 select Tr Type WE, Print Version 3, maintain Print Item as 1.
Now Go to MB90 select out put type as WE03 trns. medium as 1 and take printout
REWARD IF HELPFUL.
Regards,
Cheatn.

Print out of Layout

Hi,
Need suggestion for getting print out put of GRN (in MIGO), Invoice verification (in MIRO) & service entry sheet. Request you to suggest on this.
Regards,
Ranjan

Hi
Check following are some of steps for GR collective printing from SDN only
1. Maintain the Printer Name in SPRO->Matl Mgmt->Inv Mgmt and Phy Inv->Print Control->Gen Settings->Printer Setting
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 GI/Transfer Posting Documents
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 foll:
a. Default Values: Dispatch Time is 3 or 4 as per reqmt. and Tr medium is 1
b. Print Parameter is 7
6. In SPRO->Matl Mgmt->Inv Mgmt and Phy Inv->Output Determination->Printer Det->Pr Det by Pl/StoLoc, 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.
Regards,
Archit

Print out of GRN document.

Dear All ,
Kindly help me as user is in need to take print out of GRN document as collective slip I need to take out printout of grn.the prinout should contain collective
slip that is all item in one slip.
the slip should contain line item no.,material description,material no.,quantity,rate,total amount and sum total amount of all items together in the last page.
vendor name,p.o. no.,plant,invoice no.,invoice date,posting date,grn no.,date,location,payment terms. Pl guide that what config are to be done in SPRO .
SAP12

Hai,
Run MB02 transaction, enter material document number. Double click one line item and select messages. Separate screen will be opened to configure outputs. Give the required fields and save the document. Now Run MB90, you can take printout. Output Type: WE03 - Collective slip
Note:
Check following are some of steps for GR collective printing
1. Maintain the Printer Name in SPRO->Matl Mgmt->Inv Mgmt and Phy Inv->Print Control->Gen Settings->Printer Setting
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 GI/Transfer Posting Documents
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 foll:
a. Default Values: Dispatch Time is 3 or 4 as per reqmt. and Tr medium is 1
b. Print Parameter is 7
6. In SPRO->Matl Mgmt->Inv Mgmt and Phy Inv->Output Determination->Printer Det->Pr Det by Pl/StoLoc, 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
the slip should contain line item no.,material description,material no.,quantity,rate,total amount and sum total amount of all items together in the last page.
vendor name,p.o. no.,plant,invoice no.,invoice date,posting date,grn no.,date,location,payment terms
You have to add the requirements in the print out form - smart form with the help of ABAPer. You can find this smat form in T code NACE - slect ME Invenotry management - Output type - WE03 - Go to processing routines - form name.

SQL Server 2012 Management Studio:In the Database, how to print out or export the old 3 dbo Tables that were created manually and they have a relationship for 1 Parent table and 2 Child tables?How to handle this relationship in creating a new XML Schema?

Hi all,
Long time ago, I manually created a Database (APGriMMRP) and 3 Tables (dbo.Table_1_XYcoordinates, dbo.Table_2_Soil, and dbo.Table_3_Water) in my SQL Server 2012 Management Studio (SSMS2012). The dbo.Table_1_XYcoordinates has the following columns: file_id,
Pt_ID, X, Y, Z, sample_id, Boring. The dbo.Table_2_Soil has the following columns: Boring, sample_date, sample_id, Unit, Arsenic, Chromium, Lead. The dbo.Table_3_Water has the following columns: Boring, sample_date, sample_id, Unit, Benzene, Ethylbenzene,
Pyrene. The dbo.Table_1_XYcoordinates is a Parent Table. The dbo.Table_2_Soil and the dbo.Table_3_Water are 2 Child Tables. The sample_id is key link for the relationship between the Parent Table and the Child Tables.
Problem #1) How can I print out or export these 3 dbo Tables?
Problem #2) If I right-click on the dbo Table, I see "Start PowerShell" and click on it. I get the following error messages: Warning: Failed to load the 'SQLAS' extension: An exception occurred in SMO while trying to manage a service.
--> Failed to retrieve data for this request. --> Invalid class. Warning: Could not obtain SQL Server Service information. An attemp to connect to WMI on 'NAB-WK-02657306' failed with the following error: An exception occurred in SMO while trying
to manage a service. --> Failed to retrieve data for this request. --> Invalid class. .... PS SQLSERVER:\SQL\NAB-WK-02657306\SQLEXPRESS\Databases\APGriMMRP\Table_1_XYcoordinates>   What causes this set of error messages? How can
I get this problem fixed in my PC that is an end user of the Windows 7 LAN System? Note: I don't have the regular version of Microsoft Visual Studio 2012 in my PC. I just have the Microsoft 2012 Shell (Integrated) program in my PC.
Problem #3: I plan to create an XML Schema Collection in the "APGriMMRP" database for the Parent Table and the Child Tables. How can I handle the relationship between the Parent Table and the Child Table in the XML Schema Collection?
Problem #4: I plan to extract some results/data from the Parent Table and the Child Table by using XQuery. What kind of JOIN (Left or Right JOIN) should I use in the XQuerying?
Please kindly help, answer my questions, and advise me how to resolve these 4 problems.
Thanks in advance,
Scott Chang

In the future, I would recommend you to post your questions one by one, and to the appropriate forum. Of your questions it is really only #3 that fits into this forum. (And that is the one I will not answer, because I have worked very little with XSD.)
1) Not sure what you mean with "print" or "export", but when you right-click a database, you can select Tasks from the context menu and in this submenu you find "Export data".
2) I don't know why you get that error, but any particular reason you want to run PowerShell?
4) If you have tables, you query them with SQL, not XQuery. XQuery is when you query XML documents, but left and right joins are SQL things. There are no joins in XQuery.
As for left/right join, notice that these two are equivalent:
SELECT ...
FROM   a LEFT JOIN b ON a.col = b.col
SELECT ...
FROM   b RIGHT JOIN a ON a.col = b.col
But please never use RIGHT JOIN - it gives me a headache!
There is nothing that says that you should use any of the other. In fact, if you are returning rows from parent and child, I would expect an inner join, unless you want to cater for parents without children.
Here is an example where you can study the different join types and how they behave:
CREATE TABLE apple (a int    NOT NULL PRIMARY KEY,
b varchar(23) NOT NULL)
INSERT apple(a, b)
   VALUES(1, 'Granny Smith'),
   (2, 'Gloster'),
   (4, 'Ingrid-Marie'),
   (5, 'Milenga')
CREATE TABLE orange(c int NOT NULL PRIMARY KEY,
d varchar(23) NOT NULL)
INSERT orange(c, d)
   VALUES(1, 'Agent'),
   (3, 'Netherlands'),
   (4, 'Revolution')
SELECT a, b, c, d
FROM   apple
CROSS JOIN orange
SELECT a, b, c, d
FROM   apple
INNER JOIN orange ON apple.a = orange.c
SELECT a, b, c, d
FROM   apple
LEFT   OUTER JOIN orange ON apple.a = orange.c
SELECT a, b, c, d
FROM   apple
RIGHT OUTER JOIN orange ON apple.a = orange.c
SELECT a, b, c, d
FROM   apple
FULL OUTER JOIN orange ON apple.a = orange.c
go
DROP TABLE apple, orange
Erland Sommarskog, SQL Server MVP, [email protected]

Printing out results in case of object-relational table (Oracle)

I have made a table with this structure:
CREATE OR REPLACE TYPE Boat AS OBJECT(
Name varchar2(30),
Ident number,
CREATE OR REPLACE TYPE Type_boats AS TABLE OF Boat;
CREATE TABLE HOUSE(
Name varchar2(40),
MB Type_boats)
NESTED TABLE MB store as P_Boat;
INSERT INTO House VALUES ('Name',Type_boats(Boat('Boat1', 1)));
I am using java to print out all the results by calling a procedure.
CREATE OR REPLACE package House_boats
PROCEDURE add(everything works here)
PROCEDURE results_view;
END House_boats;
CREATE OR REPLACE Package.body House_boats AS
PROCEDURE add(everything works here) AS LANGUAGE JAVA
Name House_boats.add(...)
PROCEDURE results_view AS LANGUAGE JAVA
Name House_boats.resuts_view();
END House_boats;
However, I am not able to get Results.view working in case of object-relation table. This is how I do it in the situation of relational table.
CALL House_boats.results_view();
House_boats.java file which is loaded using LOADJAVA:
import java.sql.*;
import java io.*;
public class House_boats {
public static void results_view ()
   throws SQLException
   { String sql =
   "SELECT * from House";
   try { Connection conn = DriverManager.getConnection
("jdbc:default:connection:");
   PreparedStatement pstmt = conn.prepareStatement(sql);
   ResultSet rset = pstmt.executeQuery();
printResults(rset);
rset.close();
pstmt.close();
   catch (SQLException e) {System.err.println(e.getMessage());
static void printResults (ResultSet rset)
   throws SQLException { String buffer = "";
   try { ResultSetMetaData meta = rset.getMetaData();
   int cols = meta.getColumnCount(), rows = 0;
   for (int i = 1; i <= cols; i++)
   int size = meta.getPrecision(i);
   String label = meta.getColumnLabel(i);
   if (label.length() > size) size = label.length();
   while (label.length() < size) label += " ";
buffer = buffer + label + " "; }
buffer = buffer + "\n";
   while (rset.next()) {
rows++;
   for (int i = 1; i <= cols; i++) {
   int size = meta.getPrecision(i);
   String label = meta.getColumnLabel(i);
   String value = rset.getString(i);
   if (label.length() > size) size = label.length();
   while (value.length() < size) value += " ";
buffer = buffer + value + " "; }
buffer = buffer + "\n";   }
   if (rows == 0) buffer = "No data found!\n";
   System.out.println(buffer); }
   catch (SQLException e) {System.err.println(e.getMessage());} }
How do I print out the results correctly in my case of situation?
Thank you in advance

I have made a table with this structure:
I am using java to print out all the results by calling a procedure.
However, I am not able to get Results.view working in case of object-relation table. This is how I do it in the situation of relational table.
How do I print out the results correctly in my case of situation?
There are several things wrong with your code and methodology
1. The code you posted won't even compile because there are several syntax issues.
2. You are trying to use/test Java in the database BEFORE you get the code working outside the DB
3. Your code is not using collections in JDBC properly
I suggest that you use a different, proven approach to developing Java code for use in the DB
1. Use SIMPLE examples and then build on them. In this case that means don't add collections to the example until ALL other aspects of the app work properly.
2. Create and test the Java code OUTSIDE of the database. It is MUCH easier to work outside the database and there are many more tools to help you (e.g. NetBeans, debuggers, DBMS_OUTPUT windows, etc). Trying to debug Java code after you have already loaded it into the DB is too difficult. I'm not aware of anyone, even at the expert level, that develops that way.
3. When using complex functionality like collections first read the Oracle documentation (JDBC Developer Guide and Java Developer's Guide). Those docs have examples that are known to work.
http://docs.oracle.com/cd/B28359_01/java.111/b31225/chfive.htm
http://docs.oracle.com/cd/E11882_01/java.112/e16548/oraarr.htm#sthref583
The main issue with your example is #3 above; you are not using collections properly:
String value = rset.getString(i);
A collection is NOT a string so why would you expect that to work for a nested table?
A collection needs to be treated like a collection. You can even treat the collection as a separate result set. Create your code outside the database and use the debugger in NetBeans (or other) on this replacement code for your 'printResults' method:
static void printResults (ResultSet rset) throws SQLException {
    try {
       ResultSetMetaData meta = rset.getMetaData();
       while (rset.next()) {
           ResultSet rs = rset.getArray(2).getResultSet();
           rs.next();
           String ndx = rs.getString(1);
           Struct struct = (Struct) rs.getObject(2);
           System.out.println(struct.getSQLTypeName());
           Object [] oa = struct.getAttributes();
           for (int j = 0; j < oa.length; j++) {
              System.out.println(oa[j]);
    } catch (SQLException e) {
       System.err.println(e.getMessage());
That code ONLY deals with column 2 which is the nested table. It gets that collection as a new resultset ('rs'). Then it gets the contents of that nested table as an array of objects and prints out the attributes of those objects so you can see them.
Step through the above code in a debugger so you can SEE what is happening. NetBeans also lets you enter expressions such as 'rs' in an evaluation window so you can dynamically try the different methods to see what they do for you.
Until you get you code working outside the database don't even bother trying to load it into the DB and create a Java stored procedure.
Since your current issue has nothing to do with this forum I suggest that you mark this thread ANSWERED and repost it in the JDBC forum if you need further help with this issue.
https://forums.oracle.com/community/developer/english/java/database_connectivity
When you repost you can include a link to this current thread if you want. Once your Java code is actually working then try the Java Stored procedure examples in the Java Developer's Guide doc linked above.
At the point you have any issues that relate to Java stored procedures then you should post them in the SQL and PL/SQL forum
https://forums.oracle.com/community/developer/english/oracle_database/sql_and_pl_sql

GR slip print-out & automatic default for the print tick

Hi,
I have followed the steps as outlined below for the solution and unfortunately the GRN document do not print as anticipated. I was wondering if the non-assignment of the MM or FI Program might be the cause? Please advice if I had missed something to allow this to print immediately.
1. Maintain the Printer Name in SPRO->Matl Mgmt->Inv Mgmt and Phy Inv->Print Control->Gen Settings->Printer Setting
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 GI/Transfer Posting Documents
5. In SPRO->Matl Mgmt->Inv Mgmt and Phy Inv->Output Determination->Maintain Output Types, for the Output types WE01, WE02 and WE03, (for returns use WE03) ensure the foll:
a. Default Values: Dispatch Time is 3 or 4 as per reqmt. and Tr medium is 1
b. Print Parameter is 7
6. In SPRO->Matl Mgmt->Inv Mgmt and Phy Inv->Output Determination->Printer Det->Pr Det by Pl/StoLoc, 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.
Edited by: JML Nkgapele on Dec 1, 2008 11:10 AM

Your answer did help but still expriencing challanges with the following:
Output Types
-Print Parameters options are as follows
    >Plant/Storage location
    >Plant/Storage location/User group
    >User exit
   >User parameters
   >User
Please advice which of the above is appropriate?
-Should there be a program reflected on change output field for General data screen?
Please advice since I'm currently experiencing shotdumps(runtime errors) when processing the GR.

GR document print out

Dear All,
The user does goods receipt and the print does not comes automatically. It happens only in case of non stock items. Though I am not sure if there is any link with it but they have to go to MB02, then go to messages, put output type as WE03(GR Note Vers.3), select medium as Print output. Then only the system sends the document for print. And it is not the case with stock items. The goods receipt document for stock items goes for print automatically at the time of saving it.
What could be the problem here? Or is there any way that the user does not need to put all this data and it comes automatically.
Please suggest.
Regards
VT

Hi,
Check all the steps given below,
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.
Regards,
Prabu

GR Note Print out not comming through MB90

Dear Friends ,
We are not able to take print through MB90 , for the Goods Receipt note -3 (Collective Print Out ) .
Kindly guide me what corrections /changes I need to do.
Thanks
DGN

HI,
1. Maintain the Printer Name in SPRO->Matl Mgmt->Inv Mgmt and Phy Inv->Print Control->Gen Settings->Printer Setting
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 GI/Transfer Posting Documents
5. In SPRO->Matl Mgmt->Inv Mgmt and Phy Inv->Output Determination->Maintain Output Types, for the Output types WA01,WA02,WA03,WE01, WE02 and WE03, ensure the foll:
a. Default Values: Dispatch Time is 3 or 4 as per reqmt. and Tr medium is 1
b. Print Parameter is 7
6. In SPRO->Matl Mgmt->Inv Mgmt and Phy Inv->Output Determination->Printer Det->Pr Det by Pl/StoLoc, 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
Regards,
KK

GR slip print out

Hi All
We have a requirement to print collective GR slip for PO with multiple line items. I have setup the output type WE03 for the plant and storage location and it does print out a collective GR silp , but for this I have to change the version of the print manually in MIGO to collective from individual which is actually defaulted.
Is there way I can have the collective version defaulted depending on the number of line items I have on the PO.
please help
thanks
Vijay

The only way to default this is to add a PID to the user via SU3
NDR with value X is the parameter ID that represents the automatic population of the collective slip
Regards
Steve

Print out for Goods Issue 531

Hi
We need to take the print out of 531 mvt
What are the standerd Setting needs to maintain for the same,
Regards
Niti Narayan

hi
Check following if useful to u
1. Maintain the Printer Name in SPRO->Malt Mgmt->Inv Mgmt and Phy Inv->Print Control->Gen Settings->Printer Setting
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 GI/Transfer Posting Documents
5. In SPRO->Matl Mgmt->Inv Mgmt and Phy Inv->Output Determination->Maintain Output Types, for the Output types WA01, WA02 and WA03, ensure the foll:
a. Default Values: Dispatch Time is 3 or 4 as per reqmt. and Tr medium is 1
b. Print Parameter is 7
6. In SPRO->Matl Mgmt->Inv Mgmt and Phy Inv->Output Determination->Printer Det->Pr Det by Pl/StoLoc, maintain the Output device for all your Plants
7. Go to MN21, forWA01/02/03 and Tr Type WA, 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.
regards
KI

Print out of GR(Urgent)

Dear Experts,
I have got a requirement like this....
When user does MIGO transaction,after saving a particular document immidiately user needs a print out of that Goods Receipt.
Can any one tell me how to get this???
Thanks and Regards
MK

Hi MK
U can print GR
Do the following configurations
Pls check the below settings for material document Print out:
Before of all RUN pgm RM07NCUS in SE38
which will do all default setting automaticaly
1. Maintain the Printer Name in SPRO->Matl Mgmt->Inv Mgmt and Phy Inv->Print Control->Gen Settings->Printer Setting
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 GI/Transfer Posting Documents
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 foll:
a. Default Values: Dispatch Time is 3 or 4 as per reqmt. and Tr medium is 1
b. Print Parameter is 7
6. In SPRO->Matl Mgmt->Inv Mgmt and Phy Inv->Output Determination->Printer Det->Pr Det by Pl/StoLoc, 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.
For custom print You need to maintain below settings.
2.5.3.1. Maintain Condition Tables
Menu Path: IMG / Materials Management / Inventory Management and Physical Inventory / Output Determination/ Maintain Condition Tables
Transaction: M703
2.5.3.2. Maintain Access Sequences
Menu Path: IMG / Materials Management / Inventory Management and Physical Inventory / Output Determination/ Maintain Access Sequences
Transaction: SPRO
2.5.3.3. Maintain Output Types for IM Documents
Menu Path: IMG / Materials Management / Inventory Management and Physical Inventory / Output Determination / Maintain Output Types
Transaction: M706
2.5.3.4. Maintain Output Determination for IM Documents
Menu Path: IMG / Materials Management / Inventory Management and Physical Inventory / Output Determination / Maintain Output Determination Procedures / Condition : Procedure
2.5.3.5. Create IM Documents Condition Records
Menu Path: IMG / Materials Management / Inventory Management and Physical Inventory / Output Determination / Maintain Condition Records / Create Condition : Inventory Mgmt
Transaction: MN22
Vishal...

MIGO GR Print Out

Dear Guru's,
I am facing problem while checking collective issue tick in MIGO via Display Material Document. When I click on collective issue message appears Output save and when I press enter it resets that check.
Wats the actual problem. We are not facing this earlier. GR document and Movement Type are same as earlier and we take print out through MB90 by doing same as above.
Also I have noticed that through MB02 material document contains that check (collective issue).
This is really strange. I did not understand what is the problem. Can any1 help?
Regards,
RM

Hi,
This Problem can be overided by Maintaining the output messages in MN21
Enter the Following Data
Message type -- your Print Message type
transaction event key.--We good receipt ,WA --issue etc...
Print Version--Individual or collective
Print Item--.Material Document(1)
Partner Function -- VN
medium--Print (1)
DAte and time -- 4 (if you want immediately after Posting..
Lanuage EN.
KNow after double click on the item..or select the Item and click on the communication tab presnt at the top left hand corner.
and enter your printer details and check the print immediately option.
Hope so it helps
Regards
Anjanna

GR Print Out Put Types

Hi
Wats the diff between invidual slip and collective slip in MIGO screen
Wats the std out put type for GR print out in mb90
Vijay

hi
individual means single item per printout
collective means all items in GR
o   Individual slip (version 1)
     In this case, one GR/GI slip is printed out for each item.
o   Individual slip with inspection text (version 2)
     In this case, one GR/GI slip is printed out for each item. In
     addition, a quality inspection text is printed if there is one in
     the material master record.
o   Collective slip (version 3)
     In this case, a collective slip including all the items in a
     document is printed.
WE01, WE02 and WE03, are std output types
regards
kunal
Edited by: kunal ingale on Dec 27, 2008 9:50 AM

Print out every delivery

Dear All.
Till this day the duty-form for a company were performed through a
special Form Program, it is performed via processing routines.
The first Form Routine's name is entry.
Form was printed-out for each Transport up to now.
Current Requirements are for next time as follows:
Printing out one form for every delivery (shipment) instead of
for each Transport as so far. Please notice one Transport may
consist of many deliveries (Shipment). 1 Transport : n Shipment.
DATA:
      lc_wa_usrdata TYPE /Z2a/ty_lw_usrdata.
INCLUDE rvadtabl.
SET EXTENDED CHECK OFF.
TABLES: vbpla, thead, ttxer, ttxit, t005, vbddl, stxh, sadr."SADR40A
INCLUDE vttkdata.                      "Shipment Header
INCLUDE vttsdata.                      "Shipment Segment
INCLUDE vttpdata.                      "Shipment Items
INCLUDE vbpadata.                      "Partner
INCLUDE vtfadata.                      "Flow
INCLUDE sadrdata.                      "Address
INCLUDE vtlfdata.                      "Delivery Selection
INCLUDE vsedata.                       "shipping units
INCLUDE rv56acom.                      "I/O-Structure
SET EXTENDED CHECK ON.
TABLES: /Z2a/tv_schein.
FORM entry USING return_code us_screen.
DATA: lf_retcode TYPE sy-subrc.
screen = us_screen.
PERFORM processing USING    us_screen
                     CHANGING lf_retcode.
IF lf_retcode NE 0.
    return_code = 1.
ELSE.
    return_code = 0.
ENDIF.
ENDFORM.
FORM processing USING    proc_screen
                CHANGING cf_retcode.
DATA: ls_print_data_to_read TYPE ledlv_print_data_to_read.
DATA: ls_dlv_delnote        TYPE ledlv_delnote.
DATA: lf_fm_name            TYPE rs38l_fnam.
DATA: ls_control_param      TYPE ssfctrlop.
DATA: ls_composer_param     TYPE ssfcompop.
DATA: ls_recipient          TYPE swotobjid.
DATA: ls_sender             TYPE swotobjid.
DATA: lf_formname           TYPE tdsfname.
DATA: ls_addr_key           LIKE addr_key.
DATA: ls_header             LIKE /Z2a/ss_pv_kopf.
DATA: tb_daten              LIKE /Z2a/ss_pv_daten OCCURS 1.
DATA: lc_va_lfnr            TYPE nrlevel.
DATA: lc_va_year            TYPE char4.
DATA: lc_va_keyseg_pv       TYPE /dca/p000_keyseg.
DATA: lc_tb_bwdat_pv        TYPE /dca/p000_ty_tb_bwdat.
DATA: lc_wa_bwdat_pv        TYPE /dca/p000_ty_wa_bwdat.
DATA: lc_wa_bwm_res_pv      TYPE /Z2a/dat_cu_pvschein.
DATA: lc_va_lifnr           TYPE kunnr.
DATA: lc_va_nr              TYPE nrnr.
DATA: lc_va_anz             TYPE /Z2a/anz_pv.
DATA: lc_va_no              TYPE /Z2a/anz_kein_pv.
DATA: lc_wa_pvschein        LIKE /Z2a/tv_schein.
DATA: lc_va_line            LIKE sy-tabix.
DATA: lc_va_flag_zoll       TYPE segal,
        lc_va_rqident         TYPE rspoid,
        lc_va_vsart           TYPE vsarttr,
        lc_va_tknum           TYPE tknum.
DATA: lc_va_obj             TYPE nrobj.
DATA: lc_va_printer         TYPE rspopname.
DATA: lc_va_pv_kz           TYPE char4.
DATA: lc_va_tplst           TYPE tplst.
* SmartForm from customizing table TNAPR
lf_formname = tnapr-sform.
* determine print data
PERFORM set_print_data_to_read USING    lf_formname
                                 CHANGING ls_print_data_to_read
                                 cf_retcode.
IF cf_retcode = 0.
* select print data
    PERFORM get_data_pv TABLES   tb_daten
                        CHANGING ls_header
                                 lc_va_flag_zoll
                                 lc_va_vsart
                                 lc_va_tplst
                                 cf_retcode.
ENDIF.
lc_va_tknum = nast-objky.
IF cf_retcode = 0.
ELSE.
    PERFORM protocol_nast_update.
    cf_retcode = 4.
    EXIT.
ENDIF.
IF cf_retcode = 0.
* determine smartform function module for delivery note
    CALL FUNCTION 'SSF_FUNCTION_MODULE_NAME'
         EXPORTING formname           = lf_formname
         IMPORTING fm_name            = lf_fm_name
         EXCEPTIONS no_form            = 1
                    no_function_module = 2
                    OTHERS             = 3.
    IF sy-subrc <> 0.
    ENDIF.
ENDIF.
DESCRIBE TABLE tb_daten LINES lc_va_line.
IF lc_va_line <> 0.
    lc_va_pv_kz = 'JA'.
    SELECT SINGLE lifnr
      FROM vtpa
      INTO lc_va_lifnr
     WHERE vbeln = nast-objky
       AND parvw = 'YL'.
    lc_va_keyseg_pv = ls_header-kunnr.
    lc_va_keyseg_pv+10(10) = lc_va_lifnr.
    lc_va_keyseg_pv+20(2) = lc_va_vsart.
    lc_va_keyseg_pv+22(4) = lc_va_pv_kz.
    CALL FUNCTION '/ZTR/P000_MCDATA_FROM_'
         EXPORTING
              cv_va_keytyp = '/Z2a/KEY_CU_PVSCHEIN'
              cv_va_keyseg = lc_va_keyseg_pv
         TABLES
              cr_tb_bwdat = lc_tb_bwdat_pv.
    IF lc_tb_bwdat_pv[] IS INITIAL.
      cf_retcode = 4.
    ELSE.
      LOOP AT lc_tb_bwdat_pv INTO lc_wa_bwdat_pv.
        lc_wa_bwm_res_pv = lc_wa_bwdat_pv-datseg.
        lc_va_obj = lc_wa_bwm_res_pv(10).
        lc_va_nr = lc_wa_bwm_res_pv+10(2).
        lc_va_anz = lc_wa_bwm_res_pv+12(8).
        lc_va_printer = lc_wa_bwm_res_pv+20(4).
        SELECT SINGLE pvno
          FROM /Z2a/tv_schein
          INTO lc_va_lfnr
         WHERE tknum = nast-objky.
        IF sy-subrc = 0.
        ELSE.
          CALL FUNCTION 'NUMBER_GET_NEXT'
            EXPORTING
          nr_range_nr                   = lc_va_nr
          object                        = lc_va_obj
           IMPORTING
             number                     = lc_va_lfnr
          IF sy-subrc <> 0.
          ENDIF.
        ENDIF.
      ENDLOOP.
    ENDIF.
*   call smartform delivery note
    ls_composer_param-tddest = lc_va_printer.
*    ls_control_param-device = lc_va_printer.
    lc_va_year = sy-datum(4).
    PERFORM set_print_param USING    ls_addr_key
                                     lc_va_lfnr
                            CHANGING ls_control_param
                                     ls_composer_param
                                     ls_recipient
                                     ls_sender
                                     cf_retcode.
    lc_wa_usrdata-mandt = sy-mandt.
    lc_wa_usrdata-udate = sy-datum.
    lc_wa_usrdata-uzeit = sy-uzeit.
    lc_wa_usrdata-usr    = sy-uname.
    lc_wa_usrdata-sysid = sy-sysid.
    DO lc_va_anz TIMES.
      CALL FUNCTION lf_fm_name
           EXPORTING
                    archive_index        = toa_dara
                    archive_parameters   = arc_params
                    control_parameters   = ls_control_param
                    mail_recipient       = ls_recipient
                    mail_sender          = ls_sender
                    output_options       = ls_composer_param
                    user_settings        = ' '
                    ls_header            = ls_header
                    lc_va_lfnr           = lc_va_lfnr
                    lc_va_year           = lc_va_year
                    lc_va_tplst          = lc_va_tplst
                    lc_wa_usrdata        = lc_wa_usrdata
          TABLES
                    tb_daten             = tb_daten
         EXCEPTIONS formatting_error     = 1
                    internal_error       = 2
                    send_error           = 3
                    user_canceled        = 4
                    OTHERS               = 5.
      IF sy-subrc <> 0.
      ENDIF.
    ENDDO.
ELSE.
    lc_va_pv_kz = 'NEIN'.
    SELECT SINGLE lifnr
      FROM vtpa
      INTO lc_va_lifnr
     WHERE vbeln = nast-objky
       AND parvw = 'YL'.
    lc_va_keyseg_pv = ls_header-kunnr.
    lc_va_keyseg_pv+10(10) = lc_va_lifnr.
    lc_va_keyseg_pv+20(2) = lc_va_vsart.
    lc_va_keyseg_pv+22(4) = lc_va_pv_kz.
    CALL FUNCTION '/ZTR/P000_MCDATA_FROM_'
         EXPORTING
              cv_va_keytyp = '/Z2a/KEY_CU_PVSCHEIN'
              cv_va_keyseg = lc_va_keyseg_pv
         TABLES
              cr_tb_bwdat = lc_tb_bwdat_pv.
    IF lc_tb_bwdat_pv[] IS INITIAL.
      cf_retcode = 4.
    ELSE.
      LOOP AT lc_tb_bwdat_pv INTO lc_wa_bwdat_pv.
        lc_wa_bwm_res_pv = lc_wa_bwdat_pv-datseg.
        lc_va_obj = lc_wa_bwm_res_pv(10).
        lc_va_nr = lc_wa_bwm_res_pv+10(2).
        lc_va_anz = lc_wa_bwm_res_pv+12(8).
        lc_va_printer = lc_wa_bwm_res_pv+20(4).
        SELECT SINGLE pvno
          FROM /Z2a/tv_schein
          INTO lc_va_lfnr
         WHERE tknum = nast-objky.
        IF sy-subrc = 0.
          UPDATE /Z2a/tv_schein
          SET flag_pv = ' '
          WHERE tknum = nast-objky.
        ELSE.
* laufende nummer füllen, bei keinen PV-Teilen Nummernkreis 99
          CALL FUNCTION 'NUMBER_GET_NEXT'
            EXPORTING
          nr_range_nr                   = lc_va_nr
          object                        = lc_va_obj
*    QUANTITY                      = '1'
*   SUBOBJECT                     = ' '
*   TOYEAR                        = '0000'
*   IGNORE_BUFFER                 = ' '
           IMPORTING
             number                     = lc_va_lfnr
*   QUANTITY                      =
*   RETURNCODE                    =
* EXCEPTIONS
*   INTERVAL_NOT_FOUND            = 1
*   NUMBER_RANGE_NOT_INTERN       = 2
*   OBJECT_NOT_FOUND              = 3
*   QUANTITY_IS_0                 = 4
*   QUANTITY_IS_NOT_1             = 5
*   INTERVAL_OVERFLOW             = 6
*   BUFFER_OVERFLOW               = 7
*   OTHERS                        = 8
          IF sy-subrc <> 0.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
*         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
          ENDIF.
        ENDIF.
      ENDLOOP.
      lc_va_year = sy-datum(4).
      ls_composer_param-tddest = lc_va_printer.
      PERFORM set_print_param USING    ls_addr_key
                                       lc_va_lfnr
                              CHANGING ls_control_param
                                       ls_composer_param
                                       ls_recipient
                                       ls_sender
                                       cf_retcode.
      lc_wa_usrdata-mandt = sy-mandt.
      lc_wa_usrdata-udate = sy-datum.
      lc_wa_usrdata-uzeit = sy-uzeit.
      lc_wa_usrdata-usr    = sy-uname.
      lc_wa_usrdata-sysid = sy-sysid.
      DO lc_va_anz TIMES.
        CALL FUNCTION lf_fm_name
             EXPORTING
                      archive_index        = toa_dara
                      archive_parameters   = arc_params
                      control_parameters   = ls_control_param
                      mail_recipient       = ls_recipient
                      mail_sender          = ls_sender
                      output_options       = ls_composer_param
                      user_settings        = ' '
                      ls_header            = ls_header
                      lc_va_lfnr           = lc_va_lfnr
                      lc_va_year           = lc_va_year
                      lc_va_tplst          = lc_va_tplst
                      lc_wa_usrdata        = lc_wa_usrdata
            TABLES
                      tb_daten             = tb_daten
           EXCEPTIONS formatting_error     = 1
                      internal_error       = 2
                      send_error           = 3
                      user_canceled        = 4
                      OTHERS               = 5.
        IF sy-subrc <> 0.
        ENDIF.
      ENDDO.
    ENDIF.
ENDIF.
SELECT SINGLE *
    FROM /Z2a/tv_schein
    INTO lc_wa_pvschein
   WHERE tknum = nast-objky.
IF sy-subrc = 0.
ELSE.
    IF NOT lc_va_lfnr IS INITIAL.
      lc_wa_pvschein-mandt = sy-mandt.
      lc_wa_pvschein-tknum = nast-objky.
      INSERT INTO /Z2a/tv_schein
      VALUES lc_wa_pvschein.
      UPDATE /Z2a/tv_schein SET
      pvno = lc_va_lfnr
      vsart = lc_va_vsart
      exti1 = ls_header-schiffname
      signi = ls_header-siegel
      flag_zoll = lc_va_flag_zoll
      exti2 = ls_header-contnr
      lifex = ls_header-mbcnr
      dalen = ls_header-dalen
      dptbg = ls_header-dptbg
      kunnr = ls_header-kunnr
      add03 = ls_header-add03
      parnr = lc_va_lifnr
      datum_druck = sy-datum
      uzeit_druck = sy-uzeit
      ernam_druck = sy-ucomm
      WHERE tknum = nast-objky.
      IF tb_daten IS INITIAL.
        UPDATE /Z2a/tv_schein SET
       flag_pv = ' '
       WHERE tknum = nast-objky.
      ELSE.
        UPDATE /Z2a/tv_schein SET
        flag_pv = 'X'.
      ENDIF.
    ENDIF.
ENDIF.
* get SmartForm protocoll and store it in the NAST protocoll
* PERFORM ADD_SMFRM_PROT.                       DEL_HP_335958
ENDFORM.
FORM get_data_pv TABLES   lc_tb_daten
                 CHANGING cs_header TYPE /Z2a/ss_pv_kopf
                          lc_va_flag_zoll TYPE segal
                          lc_va_vsart TYPE vsarttr
                          lc_va_tplst TYPE tplst
                          cf_retcode.
TYPES: BEGIN OF ty_wa_vbeln,
         vbeln TYPE vbeln_vl,
         END OF ty_wa_vbeln,
         ty_tb_vbeln TYPE STANDARD TABLE OF ty_wa_vbeln
                     WITH DEFAULT KEY
                     INITIAL SIZE 0,
         ty_wa_lips LIKE lips,
         ty_tb_lips TYPE STANDARD TABLE OF ty_wa_lips
                    WITH DEFAULT KEY
                    INITIAL SIZE 0.
DATA: lc_tb_cond LIKE /Z2a/ss_pv_daten OCCURS 1.
DATA: lc_wa_daten TYPE /Z2a/ss_pv_daten.
DATA: lc_wa_cond TYPE /Z2a/ss_pv_daten.
DATA: lc_va_tknum TYPE tknum,
        lc_tb_lips TYPE ty_tb_lips,
        lc_wa_lips TYPE ty_wa_lips,
        lc_va_kunnr TYPE kunnr,
        lc_va_pvvkz TYPE /Z2a/pvvkz,
        lc_va_exprf TYPE exprf,
        lc_va_matnr TYPE matnr,
        lc_va_menge TYPE lfimg.
DATA: lc_tb_vbeln TYPE ty_tb_vbeln,
        lc_wa_vbeln TYPE ty_wa_vbeln,
        lc_va_land1 TYPE land1,
        lc_va_lifnr TYPE lifnr.
DATA: lc_va_exnum TYPE exnum.
DATA: lc_va_keyseg TYPE /dca/p000_keyseg.
DATA: lc_tb_bwdat TYPE /dca/p000_ty_tb_bwdat.
DATA: lc_wa_bwdat TYPE /dca/p000_ty_wa_bwdat.
DATA: lc_wa_bwm_result TYPE /Z2a/dat_cu_pvabwicklung.
DATA language LIKE nast-spras.
DATA shipment_number LIKE vttk-tknum.
CLEAR cf_retcode.
* get data
language = nast-spras.
shipment_number = nast-objky.
CALL FUNCTION 'RV_SHIPMENT_PRINT_VIEW'
       EXPORTING
            shipment_number     = shipment_number
            option_tvtk         = 'X' "Shipmenttype J/N
            option_ttds         = 'X' "Disposition J/N
            language            = language
            option_items        = 'X' "Transport Items J/N
            option_segments     = 'X' "Transport Segments J/N
            option_partners     = 'X' "Partners J/N
            option_sales_orders = 'X' "Sales orders J/N
            option_export_data = 'X' "Export data J/N
            option_packages     = 'X' "Packages J/N
            option_flow         = ' ' "Flow J/N
            option_no_refresh   = ' ' "Refresh Tables J/N
       IMPORTING
            f_vttkvb            = vttkvb "Shipment Header
            f_tvtk              = tvtk "Shipmenttype
            f_tvtkt             = tvtkt "Description Shipmenttype
            f_ttds              = ttds "Disposition
            f_ttdst             = ttdst "Description Disposition
            f_vbpla             = vbpla "Packages
       TABLES
            f_vttp              = xvttp "Shipment Items
            f_trlk              = slk "Delivery
            f_trlp              = slp "Delivery Item
            f_vtts              = xvtts "Shipment Segments
            f_vtsp              = xvtsp "Segments/Items
            f_vbpa              = xvbpa "Partner
            f_vbadr             = xvbadr "Address
            f_vtfa              = xvtfa "Flow
            f_vbplk             = xvbplk "Shipment Unit Header
            f_vbplp             = xvbplp "Shipment Unit
            f_vbpls             = xvbpls "Shipment Unit Sum
       EXCEPTIONS
            not_found           = 1.
cs_header-tknum      = nast-objky.
cs_header-schiffname = vttkvb-exti1.
cs_header-abfahrt    = vttkvb-dptbg.
cs_header-contnr     = vttkvb-exti2.
cs_header-normt      = vttkvb-add01.
cs_header-siegel     = vttkvb-signi.
cs_header-gewbr      = vttkvb-text2.
cs_header-gewnt      = vttkvb-text3.
cs_header-dalen      = vttkvb-dalen.
cs_header-dptbg      = vttkvb-dptbg.
cs_header-add03      = vttkvb-add03.
lc_va_tplst          = vttkvb-tplst.
lc_va_vsart = vttkvb-vsart.
SELECT vbeln
    FROM vttp
    INTO TABLE lc_tb_vbeln
   WHERE tknum = lc_va_tknum.
LOOP AT lc_tb_vbeln INTO lc_wa_vbeln.
    SELECT SINGLE kunnr lifex
      FROM likp
      INTO (lc_va_kunnr, cs_header-mbcnr)
     WHERE vbeln = lc_wa_vbeln-vbeln.
    SELECT *
      FROM lips
      INTO TABLE lc_tb_lips
     WHERE vbeln = lc_wa_vbeln-vbeln.
ENDLOOP.
LOOP AT lc_tb_lips INTO lc_wa_lips.
    SELECT SINGLE pvvkz
      FROM /Z2a/ldm_kun
      INTO lc_va_pvvkz
     WHERE kunnr = lc_va_kunnr.
    IF lc_va_pvvkz NE 'X'.
      cf_retcode = 4.
      EXIT.
    ELSE.
      SELECT SINGLE exnum segal
       FROM eikp
       INTO (lc_va_exnum, lc_va_flag_zoll)
      WHERE refnr = lc_wa_lips-vbeln.
      SELECT SINGLE exprf
        FROM eipo
        INTO lc_va_exprf
       WHERE exnum = lc_va_exnum
         AND expos = lc_wa_lips-posnr.
      lc_va_keyseg = lc_va_exprf.
      CALL FUNCTION '/ZTR/P000_MCDATA_FROM_'
           EXPORTING
                cv_va_keytyp = '/Z2a/KEY_CU_PVABWICKLUNG'
                cv_va_keyseg = lc_va_keyseg
           TABLES
                cr_tb_bwdat = lc_tb_bwdat.
      IF NOT lc_tb_bwdat[] IS INITIAL.
        LOOP AT lc_tb_bwdat INTO lc_wa_bwdat.
          lc_wa_bwm_result = lc_wa_bwdat-datseg.
          IF lc_wa_bwm_result-pv_relevant = 'X'.
* Kumulieren
            lc_wa_cond-matnr = lc_wa_lips-matnr.
            SELECT SINGLE maktx
              FROM makt
              INTO lc_wa_cond-arktx
             WHERE matnr = lc_wa_lips-matnr
               AND spras = 'DE'.
            lc_wa_cond-menge = lc_wa_lips-lfimg.
            lc_wa_cond-me    = lc_wa_lips-meins.
            COLLECT lc_wa_cond INTO lc_tb_cond.
          ENDIF.
        ENDLOOP.
      ENDIF.
    ENDIF.
ENDLOOP.
cs_header-kunnr = lc_va_kunnr.
SELECT SINGLE name1 name2 land1
    INTO (cs_header-name1,
          cs_header-name2,
          lc_va_land1)
     FROM kna1
    WHERE kunnr = lc_va_kunnr.
SELECT SINGLE landx
    INTO cs_header-land
    FROM t005t
   WHERE spras = sy-langu
     AND land1 = lc_va_land1.
* Sortieren Aufsteigend nach Materialnr
SORT lc_tb_cond ASCENDING BY matnr.
* Übergabe an Ausgabetabelle
LOOP AT lc_tb_cond INTO lc_wa_cond.
    MOVE-CORRESPONDING lc_wa_cond TO lc_wa_daten.
    APPEND lc_wa_daten TO lc_tb_daten.
ENDLOOP.
ENDFORM.                    " get_data_spat
FORM set_print_data_to_read
         USING    if_formname LIKE tnapr-sform
         CHANGING cs_print_data_to_read TYPE ledlv_print_data_to_read
                  cf_retcode.
FIELD-SYMBOLS: <fs_print_data_to_read> TYPE xfeld.
DATA: lt_fieldlist TYPE tsffields.
DATA: ls_fieldlist TYPE LINE OF tsffields.
DATA: lf_field1 TYPE LINE OF tsffields.
DATA: lf_field2 TYPE LINE OF tsffields.
DATA: lf_field3 TYPE LINE OF tsffields.
CALL FUNCTION 'SSF_FIELD_LIST'
    EXPORTING
      formname                = if_formname
*     VARIANT                 = ' '
    IMPORTING
      fieldlist               = lt_fieldlist
   EXCEPTIONS
     no_form                  = 1
     no_function_module       = 2
     OTHERS                   = 3.
IF sy-subrc <> 0.
    cf_retcode = sy-subrc.
    CLEAR lt_fieldlist.
ELSE.
* set print data requirements
    LOOP AT lt_fieldlist INTO ls_fieldlist.
      SPLIT ls_fieldlist AT '-' INTO lf_field1 lf_field2 lf_field3.
* <<<< START_OF_INSERTION_HP_350342 >>>>
      IF lf_field1 = 'IS_DLV_DELNOTE' AND lf_field2 = 'IT_SERNR'.
        lf_field2 = 'IT_SERNO'.
      ENDIF.
* <<<< END_OF_INSERTION_HP_350342 >>>>
      ASSIGN COMPONENT lf_field2 OF STRUCTURE
                       cs_print_data_to_read TO <fs_print_data_to_read>.
      IF sy-subrc = 0.
        <fs_print_data_to_read> = 'X'.
      ENDIF.
    ENDLOOP.
* header data is always required
    cs_print_data_to_read-hd_gen = 'X'.
* adress is always required for print param
    cs_print_data_to_read-hd_adr = 'X'.
* organisational data is always required for include texts
    cs_print_data_to_read-hd_org = 'X'.
ENDIF.
ENDFORM.                    " set_print_data_to_read
*&      Form set_print_param
*       text
*      -->P_LS_ADDR_KEY text
*      <--P_LS_CONTROL_PARAM text
*      <--P_LS_COMPOSER_PARAM text
*      <--P_LS_RECIPIENT text
*      <--P_LS_SENDER text
*      <--P_CF_RETCODE text
FORM set_print_param USING    is_addr_key LIKE addr_key
*                              lc_va_tknum
                              lc_va_lfnr TYPE nrlevel
                     CHANGING cs_control_param TYPE ssfctrlop
                              cs_composer_param TYPE ssfcompop
                              cs_recipient TYPE swotobjid
                              cs_sender TYPE swotobjid
                              cf_retcode TYPE sy-subrc.
DATA: ls_itcpo     TYPE itcpo.
DATA: lf_repid     TYPE sy-repid.
DATA: lf_device    TYPE tddevice.
DATA: ls_recipient TYPE swotobjid.
DATA: ls_sender    TYPE swotobjid.
DATA: lc_va_suffix TYPE rspo2name.
lf_repid = sy-repid.
CALL FUNCTION 'WFMC_PREPARE_SMART_FORM'
       EXPORTING
            pi_nast       = nast
            pi_addr_key   = is_addr_key
            pi_repid      = lf_repid
       IMPORTING
            pe_returncode = cf_retcode
            pe_itcpo      = ls_itcpo
            pe_device     = lf_device
            pe_recipient = cs_recipient
            pe_sender     = cs_sender.
SHIFT lc_va_lfnr LEFT DELETING LEADING '0'.
CONCATENATE 'PV' lc_va_lfnr INTO lc_va_suffix.
IF cf_retcode = 0.
    MOVE-CORRESPONDING ls_itcpo TO cs_composer_param.
    cs_composer_param-tdsuffix2   = lc_va_suffix.
    cs_control_param-device      = lf_device.
    cs_control_param-no_dialog   = 'X'.
    cs_control_param-preview     = screen.
    cs_control_param-getotf      = ls_itcpo-tdgetotf.
    cs_control_param-langu       = nast-spras.
ENDIF.
ENDFORM.                    " set_print_param
FORM protocol_nast_update.
CALL FUNCTION 'NAST_PROTOCOL_UPDATE'
       EXPORTING
            msg_arbgb = '/Z2a/PVSCHEIN'
            msg_nr    = '001'
            msg_ty    = 'E'
*              MSG_V2    = SYST-MSGV2
*              MSG_V3    = SYST-MSGV3
*              MSG_V4    = SYST-MSGV4
*              MSG_V1    = SYST-MSGV1
       EXCEPTIONS
            OTHERS    = 1.
ENDFORM.

Hello!
I have to customize the enclosed source code so it does the following:
print out for each shipment (see FuBa:RV_SHIPMENT_PRINT_VIEW
parameter slp) really seperated by for every shipment item LIKP-VBELN
and not for the whole VTTP-TKNUM.
The parameter "slp" must be stripted so by leaving
of the routine "get_data_pv" has only the datas of the current
LIKP-VBELN, and in the next step taking the next LIKP-VBELN
and so on. Right now it performs only one time for one VTTP-TKNUM.
If you don't understand VTTP-TKNUM and LIKP-VBELN please refer
to Transaction SE11.
Reagrds
Ilhan

GR print out- collective

Similar Messages

Maybe you are looking for