Search Toolbox.

com My Home
Topics
People Companies Jobs White Paper Library
Home Blogs Groups Wiki Communities White Papers Q&A and Docs Directory Events Subscriptions
Ads by Google
Toolbox for IT Topics SAP Blogs
Tweet 0 0 0
My Brain on Output Control: A Contented Glow
Emmanuel Hadzipetros Sep 21, 2009 | Comments (6)
The gods are known to adle men's brains and sometimes for no good reason at all. Of
course, some men are born with their brains already adled independently of the gods'
intentions or desires. Odysseus was known as a sly and devious scoundrel with
countless tricks up his sleeve but even this supposedly quick and nimble mind ran up
against the wall of the gods' malevolent indifference when he tried to understand how to
generate an IDoc from a business document in SAP using output control.
With all these mixed metaphors running out of his mouth, you can't blame the gods for
wanting to scramble his brains a little bit more thus saving the language from further
outrage. And while SAP is no god, it does sometimes seem to delight in its ability to
confuse and to obfuscate. It's no wonder then that Odysseus couldn't figure it out. He
preferred instead to lose himself in dalliance with the enchantress Circe or in the land of
the lotus eaters, where memory is always misplaced and substituted with pleasures of a
more corporal and sedentary nature.
I'd better pull out of this linguistic freefall before I lose myself in my reveries. In the end,
the mists cleared from my mind and it was right in front of my nose. Don't worry about
understanding. Just do it. Identify the configuration steps that you need to output an
IDoc. Understanding will come in its own time, which it did, after following the code in
the ABAP debugger.
To really understand it, you need to understand the tables that are read, the order in
which they are read, what data the system picks up from each table, and how it all
works together to decide that an INVOIC IDoc needs to be generated for the billing
document that is being built from a completed delivery and order for Gordy's Galaxy of
Games & B Flix, the most important customer of our imaginary studio Acme Pictures.
Another of my long and winding sentences that point to another key requirement: you
need to understand the business process, in this case, the order to cash cycle, and the
document and process flow that leads from the customer's purchase order to the SAP
sales order, the delivery document, picking, accounting updates, and the invoice.
But this is all beyond the scope of the current posting. There's a lot of documentation on
all this stuff and a good place to start is in SAP Help. Of course I cover some of it in my
new book from SAP Press Architecting EDI with SAP IDocs, at least as far as it concerns
EDI in my relatively uncomplicated scenario. But frankly if you need my help in
understanding basic SD processes you really are a newbie and probably out of your
depth. I just hope you're not pawning yourself off to some unsuspecting client as an EDI
expert.
Stepping Out with the Config
So let's step through the configuration. Our aim is to generate an INVOIC message type
using basic type INVOIC02 from a billing document in Acme's SAP system. Gordy's
Galaxy of Games & B Flix is the sold-to, bill-to, and the payer partner and their SAP
customer number is GRDY01. Gordy's partner functions are defined in the customer
master record in Acme's SAP system.
We begin by running transaction NACE. All the output pieces are here. The application
that we'll use is V3 Billing, which groups together output types for billing documents
within the SD module. The three SD applications Sales, Shipping, and Billing are
illustrated in the screen shot below.
Go with Gmail | Mail.Google.com
Mail.Google.com Free Email by Google Switch to Gmail, Sign up now!
Recommend 0 Share Share
Your email address FOLLOW
BEGIN NOW
Share:
Links
Categories
GO
A Consultant's Odyssey
by Emmanuel Hadzipetros SAP EDI Consultant
Odysseus is a hands-on ABAP and GIS developer who
loves to share his discoveries in that mysterious realm
where all problems can ... more
Receive the latest blog posts:
Share Your Perspective
Share your professional knowledge and experience
with peers. Start a blog on Toolbox for IT today!
My Book: Architecting EDI with SAP IDocs
My SDN Blog
My Humble Website
Kevin Benedict's EDI, B2B, SAP and Cloud Computing
Blog
SAP Home
SAP Developers Network (SDN)
SAP Help Portal
Search SAP
Google SAP Resources
Upgradeables Plus
SAP Professionals
Sterling Commerce
ASC X12 Standards Committee
W3C Standards
New to Toolbox? Ask A Question Join
My Brain on Output Control: A Contented Glow http://it.toolbox.com/blogs/ehadzipetros/my-brain-on-output-control-a-con...
1 of 6 3/22/2013 3:58 PM
We'll need an output type. Select V3 Billing and click the Output types button. On the
left is the dialog structure used for navigation. On the right is a table control listing all
output types. The standard output type for an invoice is RD00. We've copied RD00 into
our custom output type ZD00, but we can just as easily use the standard. RD00 can be
used to print, fax, or generate an IDoc for EDI or ALE. Our custom ZD00 has been
restricted to only generate IDocs for EDI. In our imaginary implementation, we'll use
separate custom output types that will be restricted to either printing, EDI, and faxing.
This is not an uncommon scenario and the outputs are easy to copy and edit.
We'll stick with my ZD00. We don't have to do anything here. Just look. Double-click
ZD00 (or RD00) to open the Output Type Details screen, as in the next screen shot.
The only thing we really care about here is the Access Sequence. This is where the
conditioning technique, the logic that determines what is needed, kicks in. We're using
Access Sequence 0003 SalesOrg/DistrCh/Div/Customer for Sales Organization,
Distribution Channel, Division, and Customer.
These values define a table key that the system will use to read the condition tables to
figure out what needs to be generated for a billing document just before it's saved.
Double-click Access Sequence 0003 to open the Access Sequences Overview screen.
Select Access Sequence 0003 and double-click the Accesses folder to open the
Accesses Overview, as illustrated in the screen shot below. This opens a table that lists
a number of key field sequences that can be used to drive selection of our IDoc output
from the billing document.
Access the Key
Select Access number 10 SalesOrg/DistrCh/Div/Customer and double-click on the
Fields folder. Note the four key fields from the communication structure KOMKBV3.
Structure KOMKBV3 is populated at run-time. It's used by the system to communicate
critical information to output determination to help it identify what output it needs to
generate for a billing document.
There's a lot of stuff here but don't sweat the details at this point. What you need to
know is that this access sequence links the billing document to our output type through
these fields. The billing document is created against a particular Sales Organization,
New to Toolbox? Ask A Question Join
My Brain on Output Control: A Contented Glow http://it.toolbox.com/blogs/ehadzipetros/my-brain-on-output-control-a-con...
2 of 6 3/22/2013 3:58 PM
Read 6 comments
Distribution Channel, and Division for one bill-to partner: GRDY01 in our example. This
is the first key piece of the puzzle.
The second piece is the outbound partner profile for bill-to customer GRDY01 with
message type INVOIC and with the message control screen pointing to output type
ZD00. But there's a little royal jelly holding these two pieces together and we'll look at
that soon.
Press F3 to get out of the Access screens and back into the Output Type Details
screen. We'll look at two last things in the output type.
Double-click on the Processing routines folder. The table control in this screen lists the
ABAP programs and their form routines called by the system for the different output
media. SAP uses form routine EDI_PROCESSING in program RSNASTED to process
IDocs for EDI. This program creates an output record in table NAST, figures out the
function it needs to call to build the IDoc, and then calls it.
The outbound Partner Profile for GRDY01, that we've already mentioned, is read by the
routine to identify the output type and the function module that builds the IDoc, through
its tie to the process code and message type in the message control screen. But
remember ... before you lick your chops to dig into the code, we're just looking here.
Finally, double-click the Partner functions folder, as in the screen shot. The table control
lists the partner types that will trigger output processing for the billing document, in this
case the bill-to partner, which is pretty standard, although this to can get a little funky
but we're not going there.
Use F3 to back all the way out of the output type screens and return to the main
conditions screen for transaction NACE. Select V3 Billing and click the Procedure
button. As the name implies, this provides procedures, or rules, for generating the IDoc.
Select V10000 for Billing (EDI) Output and double-click the Control folder to open the
Control Overview screen.
All the output types will be listed in the table control. ZD00 (and RD00) has a
requirement value of 62. Requirements are blocks of standard or custom ABAP code
saved in a form routine called during output processing that imposes rules on when the
IDoc is generated from the billing document.
This code checks that certain conditions are met before the IDoc can be created. The
code in requirement 62 ensures that the delivery is complete and accounting documents
have posted before it allows generation of the INVOIC IDoc from the billing document.
So now we're done looking at the configuration. These are the pieces that we need,
along with the Partner Profile and a condition record based on the Access Sequence for
our billing document that will tie all our output configuration together and link it to
Gordy's bill-to partner. We'll take care of this in our next posting. Hang in there ...
patience is a virtue ... we're almost there. Stay tuned.
About Odysseus: He was a sailor whose adventures during his ten-year voyage home from the
Trojan War were immortalized by Homer, whom the ancient Greeks referred to simply as The
Poet. Odysseus was a thoroughly engaging and wily scoundrel who excelled in overcoming
through his wits the many obstacles put in his path by the gods. Against all odds he persevered
and was ultimately successful in his quest to return to his home and be reunited with his family.
New to Toolbox? Ask A Question Join
My Brain on Output Control: A Contented Glow http://it.toolbox.com/blogs/ehadzipetros/my-brain-on-output-control-a-con...
3 of 6 3/22/2013 3:58 PM
More White Papers
6 Comments
Popular White Paper On This Topic
IT Checklist for ERP Vendor Evaluation
Related White Papers
Top Five Reasons to Choose SAP Services
Taking Management of Your SAP Environment to the Next Level
How To Achieve a Great and Profitable Customer Experience
Creasy Matthew Sep 21, 2009
Hi Odysseus,
I have bought your book "Architecting EDI with SAP IDocs" which is very useful.
Though this is off topic, I would like to bring this to your attention. Recently i have
implemented an inbound 820(REMADV - CREA). Whenever an REMADV IDoc gets
created, payment advices gets posted and in addition to that a BDC session is also
getting created. We don't want that BDC session getting created. How to control the
creation of BDC session for REMADV IDocs?
Thanks,
Matt
Emmanuel Hadzipetros Sep 21, 2009
Thank you, I'm glad the book is helpful to you. I hope you have some fun with it as
well. I had a lot of fun writing it. So did my editor.
I've worked with payments and REMADV a lot at two project sites. Did a lot of custom
programming on the IDoc and one designed and built the end-to-end 820-REMADV
interface in both GIS and SAP. That was a lot of fun, particularly with the very large
payments and was because of this experience that I started this blog, if you note my
earlier postings.
When you set up your profile, what process code did you choose? REMA or REMC?
REMA just creates the Payment Advice. REMC creates the Payment Advice and sets
up a batch input process for clearing, that may or may not be triggered immediately.
They call different function modules that are largely the same but REMC has additonal
logic for FI clearing. You can check this out by looking at the functions linked to the
process code.
This is probably what's happening in your system.
Creasy Matthew Sep 21, 2009
Thanks Odysseus for the info. It was definitely helpful. I am using the process
code CREA. It's still creating the payment advices plus the batch input process. Is it
normal?? Or do i have to use REMA only? I am using a userexit EXIT_SAPLIEDP_101
for find matching invoices from table BSID. I am wondering if i change the process
code, do i have to use a different user exit find matching invoices?
Thanks,
Matt
Creasy Matthew Sep 22, 2009
Hi Odysseus,
I tried testing with REMA process code also. It's still creating the batch input process
in addition to the payment advice. I am not sure why. Can you please enlighten me on
this?
Thanks,
Matt
Emmanuel Hadzipetros Sep 22, 2009
This raises the question of what exactly you're trying to do ... and I'm not here to
do your work for you, just point to stuff.
Are you trying to post a Payament Advice or a Credit or Debit Memo? CREA is usually
used for CREADV or DEBADV, both of which use basic type PEXR2002 and function
IDOC_INPUT_REMADV. It can also handle REMADV but remember that data drives
the results. I wouldn't use this if you're trying to post a Payment, and not a debit or
credit memo.
Does your IDoc actually post a Payment Advice? What transaction is being called by
the batch input session that it creates?
It's nearly impossible to analyze this without running your IDoc function through the
debugger and totally impossible to do that without getting paid for it. There is a flag in
New to Toolbox? Ask A Question Join
My Brain on Output Control: A Contented Glow http://it.toolbox.com/blogs/ehadzipetros/my-brain-on-output-control-a-con...
4 of 6 3/22/2013 3:58 PM
SUBMIT PREVIEW
We Recommend
Design Principles: Cohesion
Toolbox for IT - Knowledge Sharing
Communities
From Around The Web
If You Have Gmail... You Must Have This
(Business Insider)
How to Use Arithmetic Vector Operations
the function that controls whether or not another function is called to trigger clearing by
batch input. You'll need to debug the function or get an ABAPer to debut, unless of
course you want to hire me to do in which case I'll send you my rates offline.
Good luck.
Creasy Matthew Sep 23, 2009
Thanks............................
Leave a Comment
Connect to this blog to be notified of new entries.

You are not logged in.
Sign In to post unmoderated comments.
Join the community to create your free profile today.
Want to read more from Emmanuel Hadzipetros? Check out the blog archive.
Archive Category: EDI
Keyword Tags: Output Control Message Control SAP IDocs EDI Partner Profile
Disclaimer: Blog contents express the viewpoints of their independent authors and are not reviewed for
correctness or accuracy by Toolbox for IT. Any opinions, comments, solutions or other commentary
expressed by blog authors are not endorsed or recommended by Toolbox for IT or any vendor. If you feel
a blog entry is inappropriate, click here to notify Toolbox for IT.
From Around The Web
Recommended by
10 Web Design
Patterns for 2013
(Incion)
How 'big data' is
changing lives
(BBC)
How to Format
Paragraphs in
Photoshop CS6
(Dummies.com)
If You Have Gmail...
You Must Have This
(Inc.com)
Slide from Scratch: A
Billing/Invoicing
Process Flow
(Powerpointing
Templates)
Sneaky Rogue
Malware Disguises
Itself As Security
Software!
(Microsoft Security Blog)
Common File Storage
- A Feature To Avoid
File Duplication |
BlazeMeter
(JMeter Cloud Blog)
Eden Springs Case
Study: Does Content
Marketing Make A
Significant Difference?
(Business 2 Community)
New to Toolbox? Ask A Question Join
My Brain on Output Control: A Contented Glow http://it.toolbox.com/blogs/ehadzipetros/my-brain-on-output-control-a-con...
5 of 6 3/22/2013 3:58 PM
How to Setup a Website on the Internet -
FOR FREE
Sensible Tech Marketing
Deliverable: Project Deployment Plans
DataStage tip for beginners: developer
short cuts
in R (Dummies.com)
November Cosmo Covergirl Kate Uptons
10 Greatest (GoGoMix)
The 22 Diagram A consultants best
friend? (Powerpointing Templates)
Integration #FAIL Part 2: Lying in the
Path of an Oncoming Bus (The TIBCO
Blog)
what's this?
Recommended by
Ads by Google
Home Automation System
Samsung Range of Door Lock & VideoDoor Phone for Home and Apartments!
www.samsunghomeautomation.com
Erp
New Jobs Posted Everyday.Sign up to Apply &Find Jobs
www.monsterindia.com/contract_jobs
Wireless Smart Home
Smart Phone Home ControlTotal Home Automation Solution
www.ekonhome.com
Best Smartphone @ Rs.3999
IDEOS Android mobile with 3G+ Wifi.Rs. 1500 value back on Tata Docomo
tatadocomo.com/3g-Ideos-MobilePhone
Wings ERP for SMBs
Web-based ERP for SMBsPowerful, Flexible, Easy
www.wingsinfo.net
Collaboration Tools
Discussion Groups
Blogs
Wiki
Toolbox for IT
My Home
Topics
People
Companies
Jobs
White Paper Library
Follow Toolbox.com
Toolbox for IT on
Twitter
Toolbox.com on Twitter
Toolbox.com on
Facebook
Data Center
Data Center
Development
C Languages
Java
Visual Basic
Web Design & Development
Enterprise Applications
CRM
ERP
Infor
PeopleSoft
SAP
SCM
Siebel
Enterprise Architecture & EAI
Enterprise Architecture & EAI
Information Management
Business Intelligence
Database
Data Warehouse
Knowledge Management
Oracle
IT Management & Strategy
Emerging Technology & Trends
IT Management & Strategy
Project & Portfolio Management
Cloud Computing
Cloud Computing
Networking & Infrastructure
Hardware
Mobile & Wireless
Networking
Communications Technology
Operating Systems
Linux
UNIX
Windows
Security
Security
Storage
Storage
Topics on Toolbox for IT Toolbox.com
About
News
Privacy
Terms of Use
Work at Toolbox.com
Advertise
Contact us
Provide Feedback
Help Topics
Technical Support
Other Communities
Toolbox for HR
Toolbox for Finance
Copyright 1998-2013 Ziff Davis, Inc (Toolbox.com). All rights reserved. All product names are trademarks of their respective companies. Toolbox.com is not
affiliated with or endorsed by any company listed at this site.
New to Toolbox? Ask A Question Join
My Brain on Output Control: A Contented Glow http://it.toolbox.com/blogs/ehadzipetros/my-brain-on-output-control-a-con...
6 of 6 3/22/2013 3:58 PM