7/4/2017 SD - Output determination configuration

Home Technical Interview Q's Jobs Testimonials Contact Us

Custom Search
Topics: Output determination configuration
By Jayanta Bej, Capgemini SAPTechnical
General Topics 13,746 likes
Materials Management

Sales & Distribution Sales order confirmation

Financials 1. Maintain output types (Transaction: V/30 or Sales & Distribution -> Basic Functions -> Like Page
CRM Output -> Output determination -> Output proposal using the condition technique ->
Maintain output determination for sales document -> Maintain output types)
Production Planning Be the first of your friends to like this
Plant Maintenance
1.1. Select and copy BA00 to ZA00

HCM (HR)

Project Systems

Warehouse Management
SAPTechnical
October 5, 2014

Contribute ABAP consultants required for f

top MNC in Pune, India (Magarp
Join the Mailing List City) .

Enter name and email address below:

Experience: 4+ years in SAP
Name: Location: Pune
Joining time: 2 weeks...
Email:

550 2 13
Subscribe Unsubscribe
GO

1.2. Access sequence 0003 (Sales org / customer). If one of these is not suitable then SAPTechnical
September 16, 2014
you need to maintain condition tables

ABAP consultants required for P

1.3. Change Transmission. Medium to 6 (EDI), partner function SP (Sold to), Time (4 =
immediate)

1.4. Check access to conditions and check off multiple issuing

1.5. Save

http://www.sapfunctional.com/SD/ODC/Demo.htm 1/3
7/4/2017 SD - Output determination configuration
2. Assign output determination procedure (Transaction V/47 or Sales & Distribution ->
Basic Functions -> Output -> Output determination -> Output proposal using the
condition technique -> Maintain output determination for sales document -> Assign
output determination procedure)

2.1. Create a new entry for ZA00, medium 6, function SP and order confirmation.

3. Maintain output determination procedure (Transaction V/32 or Sales & Distribution ->
Basic Functions -> Output -> Output determination -> Output proposal using the
condition technique -> Maintain output determination for sales document -> Maintain
output determination procedure)

3.1. Check Assign output determination procedures -> Allocate sales document header
(Transaction V/43) for the Output procedure being used for order OR and BA00 and
youll find that it is linked to V10000

3.2. Select V10000 (Transaction v/32) and choose control

3.3. Add a new step for your new output type. Eg. Step 40 (Next Step in sequence),
Counter, Type = ZA00 and requirement 22 (Requirement tells when the output is
required to be fulfilled. Ie. After order confirmation, after goods issue, )

4. Create condition records (Menu path: Logistics -> Sales & Distribution -> Master data.
Output -> Sales document Create)

4.1. If required select the appropriate key combination (in this case the Sales org /
customer relationship)

http://www.sapfunctional.com/SD/ODC/Demo.htm 2/3
7/4/2017 SD - Output determination configuration

4.2. Enter the customer number (QWM000 in this case) and enter. The rest of the values
should be read in except the partner number.

4.3. Enter the required partner number (QWM000 in this case). This is the partner that
will be EDId the data. It is useful when you have multiple SAP customers that need
to send messages to 1 partner. Eg. All the Wal-Marts send their invoices to 1 office.
You would then have a list of customers, relating to each Wal-Mart, pointing to 1
Wal-Mart partner that will receive all the EDI docs.

Advance shipping notification

Similarly the output type was copied from LALE to ZALE and linked to partner QWM000

Based on when a delivery note is created (Transaction V/36)

Invoice

Similarly the output type was copied from RD00 to ZD00 and linked to partner QWM000

Based on when a delivery goods issue is posted. (Transaction V/42).

Please send us your feedback/suggestions at webmaster@SAPFunctional.COM

Home Contribute About Us Privacy Terms Of Use Disclaimer Safe Companies: Advertise on SAPFunctional.COM | Post Job Contact Us
2006-2007 SAPFunctional.COM. All rights reserved.
All product names are trademarks of their respective companies. SAPFunctional.COM, Inc. is in no way affiliated with SAP AG.
SAP, SAP R/3, R/3 software, mySAP, ABAP, BAPI, xApps, SAP NetWeaver, and and any other SAP trademarks are registered trademarks of SAP AG in Germany and in several other countries.
Every effort is made to ensure content integrity. Use information on this site at your own risk.

Graphic Design by Round the Bend Wizards

http://www.sapfunctional.com/SD/ODC/Demo.htm 3/3