teachSAP

ZEBRA Barcode Printer Setting..

2010-12-22T14:21:00.000-08:00

Teklogix

2010-11-11T14:18:00.000-08:00

Important Tables for SAP SD

2010-09-28T20:39:00.001-07:00

http://www.sap-img.com/sap-sd/important-tables-for-sap-sd.htm

Sales and Distribution:

Table Description

Customers

KNA1   General Data
                  KNB1   Customer Master – Co. Code Data (payment method, reconciliation acct)
                  KNB4   Customer Payment History
                  KNB5   Customer Master – Dunning info
                  KNBK   Customer Master Bank Data
                  KNKA   Customer Master Credit Mgmt.
                  KNKK   Customer Master Credit Control Area Data (credit limits)
                  KNVV   Sales Area Data (terms, order probability)
                  KNVI   Customer Master Tax Indicator
                  KNVP   Partner Function key
                  KNVD   Output type
                  KNVS   Customer Master Ship Data
                  KLPA   Customer/Vendor Link

Sales Documents   VBAKUK VBAK + VBUK
                  VBUK   Header Status and Administrative Data
                  VBAK   Sales Document - Header Data
                  VBKD   Sales Document - Business Data
                  VBUP   Item Status
                  VBAP   Sales Document - Item Data
                  VBPA   Partners
                  VBFA   Document Flow
                  VBEP   Sales Document Schedule Line
                  VBBE   Sales Requirements: Individual Records

SD Delivery DocumeLIPS Delivery Document item data, includes referencing PO
LIKP Delivery Document Header data

Billing Document VBRK Billing Document Header
VBRP Billing Document Item

SD Shipping Unit VEKP Shipping Unit Item (Content)
VEPO Shipping Unit Header

STOCK TRANSPORT ORDER

2010-09-15T12:01:00.001-07:00

http://architectsap.com/blog/sap/how-to-setup-stock-transport-order-between-two-storage-locations/

A

2010-07-16T04:52:00.000-07:00

SAP Wholesale - Best Practises

2010-07-02T11:01:00.001-07:00

Idoc - Batch Job for Reprocessing and other details

2010-06-29T03:05:00.000-07:00

How to Reprocess the IDOC in Both Inbound & Outbound
By: Mohamed

Check these reports:

RBDAGAIN - Process Outbound IDocs with Errors Again

Description: This report reprocesses outbound IDocs which contain errors. IDocs containing errors have one of the following statuses:

02: Error transmitting data to port

04: Error in EDI subsystem control information

05: Error in conversion

25: Continue processing despite syntax error (outbound)

29: Error in ALE service

RBDAGAIE - Reprocessing of Edited IDocs

Description: This report reprocesses an edited IDoc in inbound or outbound processing. The edited IDoc has one of the following statuses:

32: IDoc edited (outbound)

69: IDoc edited (inbound)

RBDAGAI2 - Re-processing of IDocs after ALE Input Error

Description: You use this report to reprocess inbound IDocs containing errors. IDocs containing errors have one of the following statuses:

56: IDoc containing errors added

61: Continue processing despite syntax error (inbox)

63: Error passing IDoc to the application

65: Error in ALE service

----

For Inbound

1) Goto WE19, select ur IDOC and execute. The details will be shown of IDOC. Change the data in the segment as per your requirement.

2) Click on standard inbound process. If you want to execute the process in foreground, click on standard inbound function module. Select related function module and execute the process in foreground/background.

For outbound

1) Follow same step 1.

2) Click on standard outbound processing

-----

To reprocess Idocs in outbound or inbound you can create back ground jobs using the following programs.

For Outbound:

For 02 status IDocs follow the below procedure:

1. Open SE38.

2. Give program RBDAGAIN.

3. Give you Idocs and save as variant.(Give any name)

4. Now, go to SM36,and specify a job name(Any name).

5. Now click on STEP give your Variant name in the respective field and you program name as RBDAGAIN.

6. Save and come back.

7. Now click on "START CONDITION".Here you give schedule the job either "Immediately" or "Periodically".

8. To do an immediate job select Immediate and save.Else go for perodic as you need.

9. Now save the screen on SM36.

10. To release the job click "Job selection" -- > select sceduled --> execute.

This would push your Idoc from *02*(Error passing data to port) to 30(Idoc ready to dispatch) status.

Now to send the Idoc from 30 to *03*(Data passed to port OK) use the "RSEOUT00" program and run another job as stated above.

This would send the Idocs to 03.

Similarly at Inbound side:

To reprocess an Idoc in 51 status:

Use program "RBDMANI2" and run a job.It will push Idocs from 51 to 53 status.

For 64 status use "RBDAPP01" program.

You can do it in transaction code BD87

Purchase Order: Confirmation Category

2010-05-29T04:35:00.000-07:00

http://blog.csdn.net/baiboyd/archive/2009/12/24/5068411.aspx

VAT error when posting with BAPI_ACC_INVOICE_RECEIPT_POST

2010-04-23T04:21:00.001-07:00

https://forums.sdn.sap.com/thread.jspa?threadID=1394866&tstart=0

Idoc - General Overall View

2010-04-23T02:49:00.000-07:00

http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/5212%3Fpage%3Dlast%26x-showcontent%3Doff

Note 753622 - Sending of body text and PDF attachment with medium 5

2010-04-20T05:55:00.000-07:00

https://service.sap.com/sap/support/notes/753622

Note 191470 - Purchase order as an e-mail

2010-04-20T05:45:00.001-07:00

Note 191470 - Purchase order as an e-mail

Invoice - Readsoft Program Demo

2010-04-11T14:47:00.001-07:00

ZEBRA ZM400 Barcode Printer

2010-04-11T14:19:00.001-07:00

BARCODE READER TEKLOGIX 7530

2010-04-11T14:16:00.001-07:00

Optimize Space

2010-04-11T14:13:00.001-07:00

WMS: Key Factors to consider

2010-04-11T14:12:00.001-07:00

WMS

2010-04-11T14:11:00.001-07:00

EWM

2010-04-11T02:53:00.001-07:00

ExtEndEd WarEhousE ManagEMEnt With SaP® SuPPly Chain

EWM

2010-04-11T02:51:00.001-07:00

eWM

2010-04-11T02:49:00.000-07:00

10 Amazing Life Lessons You Can Learn From Albert Einstein (Summarised)

2010-04-11T02:10:00.000-07:00

10 Amazing Life Lessons You Can Learn From Albert Einstein

1.Follow Your Curiosity. "I have no special talent. I am only passionately curious."

2.Perseverance is Priceless. "It's not that I'm so smart; it's just that I stay with problems longer."

3.Focus on the Present. "Any man who can drive safely while kissing a pretty girl is simply not giving the kiss the attention it deserves."

4.The Imagination is Powerful. "Imagination is everything. It is the preview of life's coming attractions. Imagination is more important than knowledge."

5.Make Mistakes. "A person who never made a mistake never tried anything new."

6.Live in the Moment. "I never think of the future - it comes soon enough."

7.Create Value. "Strive not to be a success, but rather to be of value."

8.Don't Expect Different Results. "Insanity: doing the same thing over and over again and expecting different results."

9.Knowledge Comes From Experience. "Information is not knowledge. The only source of knowledge is experience."

10.Learn the Rules and Then Play Better. "You have to learn the rules of the game. And then you have to play better than anyone else."

Adsense

2010-04-10T08:48:00.001-07:00

Adsense

2010-04-10T08:45:00.001-07:00

Tools

2010-04-10T08:14:00.001-07:00

70 Tools 70 Minutes

2010-04-10T07:23:00.001-07:00

Web Tools

70 Tools 70 Minutes

View more presentations from Silvia Tolisano.

Optical Archive: Not possible to display archived PO from ME23N

2010-04-08T11:40:00.001-07:00

Ref SAP: Note 304541 - Display of originals does not work in purchasing.

Also run the report MMPUR_BOR_CHANGE_ARL.

TAX AMOUNT FROM TAX PERCENTAGE

2010-04-08T05:35:00.001-07:00

CALL FUNCTION 'GET_TAX_PERCENTAGE'
EXPORTING
aland = t001-land1
datab = it_bkpf-budat
mwskz = p_bseg-mwskz
txjcd = space
TABLES
t_ftaxp = lt_ftaxp

How to find Tax Amount from Tax Percentage

2010-04-08T05:34:00.001-07:00

https://forums.sdn.sap.com/thread.jspa?threadID=880205&tstart=16801

Table: FI tolerance groups for employees

2010-04-08T05:01:00.001-07:00

Table for FI tolerance groups for employees so that Employee authorisation can be restricted based on amount in this table .....Use T043T

MRBR - Block Removal History Program

2010-04-08T04:55:00.001-07:00

Run the Report RFBABL00 to see which FI document or Invoice is changed

Idoc

2010-04-08T03:26:00.001-07:00

IDOC

Smartforms: Font Problem Arial 12 converting to courier 12 in print preview

2010-04-08T01:40:00.001-07:00

Device type was not configured with Arial font. Once the configuration was done issue is resolved.

Check if the default style is ur zstyle or not in the global settings--> form attributes ---> output options.
Because this will have default system style as 'SYSTEM' .

SPRO Configuration Compare Across Clients

2010-04-08T01:07:00.001-07:00

You can compare customizing entries across clients by using transaction OY19 or SCU0

SAP Community Network Wiki - My Home

2010-04-07T15:42:00.000-07:00

SAP Community Network Wiki - My Home

SAP Community Network Wiki - ABAP Development - LSMW

2010-04-07T15:41:00.000-07:00

SAP Community Network Wiki - ABAP Development - LSMW

SAP Community Network Wiki - ABAP Development - Creating a LSMW using Standard Batch or Direct Input Recording

2010-04-07T15:40:00.000-07:00

SAP Community Network Wiki - ABAP Development - Creating a LSMW using Standard Batch or Direct Input Recording

teachSAP - live streaming video powered by Livestream

2010-04-07T14:37:00.001-07:00

<object width="560" height="340" id="lsplayer" classid="clsid:D27CDB6E-AE6D-11cf-96B8-444553540000"><param name="movie" value="http://cdn.livestream.com/grid/LSPlayer.swf?channel=teachsap&autoPlay=false"></param><param name="allowScriptAccess" value="always"></param><param name="allowFullScreen" value="true"></param><embed name="lsplayer" src="http://cdn.livestream.com/grid/LSPlayer.swf?channel=teachsap&autoPlay=false" width="560" height="340" allowScriptAccess="always" allowFullScreen="true" type="application/x-shockwave-flash"></embed></object><div style="font-size: 11px;padding-top:10px;text-align:center;width:560px"><a href="http://www.livestream.com/teachsap?utm_source=lsplayer&utm_medium=embed&utm_campaign=footerlinks" title="Watch teachsap">teachsap</a> on livestream.com. <a href="http://www.livestream.com/?utm_source=lsplayer&utm_medium=embed&utm_campaign=footerlinks" title="Broadcast Live Free">Broadcast Live Free</a></div>

teachSAP - live streaming video powered by Livestream

A Single Mistake Can Cost You $$$$$

2010-03-30T06:05:00.001-07:00

IDOC, Mike Salvo, RBDMIDOC, SAP

Posted by ccampbell on July 9, 2009 · Leave a Comment

While working with a client on developing EDI-856 transactions with one of their trading partners, an error occurred that cost my client thousands of dollars in charge back fines.

In their SAP environment they produce a single DESADV IDoc per order/purchase order. This could amount to several hundred DESADV IDocs being generated. The initial development was a 1 to 1 translation in that each DESADV IDoc that was produced would be translated into a single EDI-856 document.

Because of a single data error, due to department procedures not being followed in the warehouse in the closing of orders, the bad data element resulted and was repeated throughout all of the DESADV IDocs that were generated. Translation of the IDocs was successful because this error was not conceived at the point of map development. The hundreds of translated documents were sent to the trading partner and subsequently resulted in failed documents.

Because the trading partner generated a charge back for each document sent, my client was billed thousands of dollars in charge back fines. This simple example shows how a single error repeated in each document can turn out to be a very costly problem.

I hope to show you in the next few postings how to bundle the IDocs together to:

Bundle and reduce the number of IDocs being translated
Reduce the number of EDI documents being sent to the trading partner
Minimize the charge back cost, should and error occur

Changing SAP IDOCs Status In Mass / Mass Deletion Of IDOCs

2010-03-30T05:55:00.001-07:00

Posted by Tim Yates on Wednesday, October 7, 2009 · Leave a Comment

Mass Change of SAP IDOC Status

From time to time it becomes necessary to change the status of SAP IDOCs in SAP. The most common scenario is the requirement to mark SAP IDOCs for deletion. There is no good way to mass mark IDOCs for deletion via the standard IDOC processing transaction BD87. However there is a program that will let you change status.

RC1_IDOC_SET_STATUS

CAUTION: This program should be used with great care and consideration. Improper use of this program can result in data consistency issues. Make sure you know what you are deleting, why you are deleting it, and what is required to correctly update you system after deleting.

Example: Marking IDOCs for Deletion In Mass

It is pretty typical for support users to set the deletion flag on IDOCs that have been incorrectly created and have errored. When there are a small number of IDOCs this is possible via transaction BD87.

An inbound IDOC in error will have the status 51, when it is marked for deletion it has a status of 68.

A view of the IDOCs to be deleted in WE05.

To mass delete IDOCs run the following program via SE38: RC1_IDOC_SET_STATUS via the SAP Transaction: SE38

There are only a few parameters on the selection screen for this program. It is most important that you correctly restrict the IDOCs you select with this program. The program automatically defaults to marking inbound IDOCs in error for deletion.

To mass select IDOCs to be marked for deletion select:

There are many options for selecting and restricting the IDOCs to Mass process. Select by single value or range. Restrict by single value or range.

The allows you to upload a list of IDOCs from a text file.

The allows you to apply a list from your clipboard.

Execute the program

Check the status of the 3 IDOCs in WE05

Example: Changing IDOCs Status To Repost

It is also possible to use this program to reset an IDOC so that it can be reprocessed.

With the following selection we are going to reset the IDOCs with status 68 marked for deletion back to status 64 to try and reprocess them.

Execute the program

As you can see, program RC1_IDOC_SET_STATUS is very helpful, but please be careful when you use it!

About Tim:

Tim has over 20 years industry experience, with 15 years concentrated on SAP and related technologies. He has broad industry exposure working with companies such as Siemens Automotive, Mercury Marine, SAP America, Eli Lilly & Company, and Verizon. Tim’s deep understanding of SAP and the industry comes from a very hands on approach. His concentration in SAP has been in systems architecture and integration, helping companies develop their infrastructure and controls to successfully integrate SAP into their existing IT landscape.

Notes in MM-PUR

2010-03-29T14:39:00.000-07:00

List of most important notes in MM-PUR

MM-PUR

30316 Problems with fields that are not ready for input in purch.

MM-PUR-GF-ACC

496082 FAQ: Account assignment in purchasing

627072 ME21N: incorrect account assignment on cost center

551863 ME21N: Accnt assignment not derived for required entry field

MM-PUR-GF-ADR

498153 FAQ: Addresses in the purchasing

821981 Change in Vendor Address in PO updates Vendor Master address

422641 ME21N, ME22N:

MM-PUR-GF-ARC

456129 FAQ: Archiving in purchasing

401318 Archiving: Additional information

335800 SARA: Deletion indicator not set, but why?

MM-PUR-GF-REL

365604 FAQ: Release strategies in purchasing

493900 FAQ: Release Strategy

86900 Transport of Release strategies (OMGQ,OMGS)

MM-PUR-GF-ARL

499625 FAQ: Optical archiving in purchasing

732278 Display of Originals does not work for archived documents

ABAP Development Workbench Basics

2010-03-28T06:45:00.000-07:00

SAP_Siemens -

SAP-MASS-CHANGE-by-Mohamed-Hasan-RifaieM

2010-03-28T06:43:00.000-07:00

SAP MASS CHANGE by Mohamed Hasan RifaieM -

SAP MASS CHANGE By M. Mohamed Hasan Rifaie

2010-03-28T06:38:00.000-07:00

SAP MASS CHANGE by Mohamed Hasan RifaieM

Dr. Edward de Bono - Edward de Bono Foundation UK

2010-03-27T09:38:00.001-07:00

Sunday Agenda - Interview with Edward de Bono..Guru of Thinking..

2010-03-27T09:19:00.001-07:00

Note 304541 - Display of originals does not work in purchasing

2010-03-25T16:46:00.000-07:00

Archiving Note 304541 - Display of originals does not work in purchasing

Note 499625 - FAQ: Optical archiving in purchasing

2010-03-25T16:45:00.000-07:00

Note 499625 - FAQ: Optical archiving in purchasing

Christopher Stoll: Local SAP Printing

2010-03-24T13:42:00.001-07:00

Local SAP Printing

With our SAP installation we have many printers defined all over the world, but sometimes we don't want to print to a real printer. Especially in IT, we can do a lot of prints to test things, and it is much more environmentally friendly (and cheaper) to print to an electronic file. For our installation there is only one way to do this, using the local SAP print daemon.

We have a specially configured printer named LOCL that will print to the default printer on the local computer using the local SAPLPD. And this is great until you need to print barcodes, there is a problem rendering them correctly probably due to the fonts. To get around this problem we also have a local post script printing option, but it is not very well known.

Instead of using the printer LOCL, we use the printer LOCO (LOCL_PS in the test systems). There is a catch to using this printer, which is probably why it isn't used more often. You must have a local printer set up with the name SAP_POST (SAP_PS for the test systems) that is configured to print to file. When you request a print on LOCO the local SAP line printer daemon searches for the SAP_POST printer and then sends postscript output to it. The system asks you for a file name, and voila, you have a post script file.

Of course the next problem is what to do with the post script file. To view it I installed Ghostscript and GhostView. And that works well for me. But, when other people need to view these outputs I have to assume that they do not have any postscript viewer installed. So, from inside of GhostView I print the label to PDF.

And that is the simplest method I have found for generating PDF output of prints containing special items such as barcodes.

Christopher Stoll: Local SAP Printing

MIR7 Park Invoice Functionality

2010-03-23T05:00:00.001-07:00

New processing functionality has been added to the MIR7 - Park Invoice Transaction. The new processes, listed below will be effective Thursday, September 9, 2004.
Paying invoices when the unit price of the invoice is less than the unit price listed in a Purchase Order (PO). An error situation will occur if one attempts to process an invoice that is $750 or 30% less than the unit price listed in a purchase order line item. This functionality is being instituted to aid in the prevention of exhausting the entire quantity of a PO line item when making partial invoice payments. The following error message will be displayed when the conditions of the tolerance are met: “Price too low (below tolerance limit of $750 or 30%”). If you encounter this error, please review and compare the quantity entered in the MIR7 transaction against the actual quantity of the invoice being paid. In most cases, changing the quantity in the MIR7 transaction to match the quantity being invoiced will resolve the error. If the invoice price is accurate and the unit price is $750 or 30% less than the unit price of the PO, please contact your local purchasing department to discuss a possible modification of the PO.
Paying invoices against expired framework orders (FOs). All invoices and credit memos for purchases made during the effective period of a framework order must take place within 60 days after the expiration date of a FO. This rule applies to all framework order types. Attempts to enter invoices or credit memos with a posting date greater than 60 days past the FO expiration date will result in the following error: “Blanket purchase order 6500000000: validity (01/01/2003 – 01/01/2004) not complied with”. If you encounter this error, please use transaction ZME_NEW_FO_NBR - Find New Purch Contract FO Nbr to determine if a new framework order has been issued for the requirements of the expired FO. This transaction is appropriate for FOs that are issued against purchasing contracts and is not applicable to department specific FOs. Input the old framework order number in the appropriate field of the displayed transaction and select the execute button. If a new FO has been issued the new FO number will be displayed. In most cases you may use the new FO number in making your invoice payment. (**A word of caution about using a new FO number – please compare the vendor in the new FO to the vendor in your invoice. If the vendor in the new FO is not the same as the vendor in the old FO – do not use the new FO number.) If an invoice is greater than 60 days past the expiration date of the FO and a new FO has not been issued, you will need to contact your local Purchasing Department to discuss your options in processing the invoice.
Determining when framework orders expire: Copies of department FOs are forwarded to the department of record and the FO document will contain the expiration date. You may also access transaction ZME_FO_EXP_DT - Framework Order Expiration Date. This transaction is applicable to all FO types. Enter the FO number or a vendor number in the selection screen that will be displayed and select the execute button. The expiration date of the FO will be displayed. Additionally, for FOs issued by the UTK Purchasing Department against purchasing contracts, you may access the UTK Purchasing web site and monitor the status of purchase contract/FO that is scheduled to expire. Once the UTK Purchasing web site is accessed - select the “Announcements link”. Instructions have been attached that will aid in adding the UTK purchasing web address in the favorites section of your SAP main menu. Please note: Purchases should not be made against a framework order after it has expired. Any questions concerning framework order validity periods or the proper framework order to use in processing an invoice should be directed to your local purchasing department for additional clarifications.

MIR7 Park Invoice Functionality

Logistics Simulation Conveyor Picking

2010-03-21T15:56:00.001-07:00

The picking and packing process

2010-03-21T15:54:00.001-07:00

Datalogic PowerScan RF Industrial Barcode Scanner

2010-03-21T15:49:00.003-07:00

RF ORDERS: Orders/Receiving

2010-03-21T15:49:00.001-07:00

Warehouse Operations

2010-03-21T15:48:00.001-07:00

Warehouse Robots at Work

2010-03-21T15:46:00.001-07:00

Warehouse Management System

2010-03-21T15:21:00.001-07:00

IBM RFID Commercial - The Future Market

2010-03-21T15:20:00.001-07:00

RFID - Technology Video

2010-03-21T15:18:00.001-07:00

RFID system for warehouse management

2010-03-21T15:17:00.001-07:00

Pallets identification and location with RFID on the forklifttruck by PHI DATA

2010-03-21T15:16:00.001-07:00

Item Locator System

2010-03-21T15:15:00.001-07:00

SAP Warehouse Project Case Study by CSI for Salton Europe Case Study

2010-03-21T15:13:00.001-07:00

RFID Wizard for EASYLABEL labelling software - LogisticsIT.com

2010-03-21T15:05:00.001-07:00

RFID Wizard for EASYLABEL labelling software

EASYLABEL's RFID Wizard allows you to easily create EPC (Electronic Product Code) and DoD (Department of Defence) smart labels.

The RFID Wizard will prompt you for the necessary information and EASYLABEL will do the rest. RFID projects that do not require the EPC or DoD RFID code can use EASYLABEL to directly program HF (High Frequency) or UHF (Ultra High Frequency) smart labels in a hexadecimal or ASCII format.

With EASYLABEL, you have the option to import parts or all of your RFID data from sources such as: databases, serial files, user input, existing bar code or text fields, and external text files. You may also choose to print the RFID data, encoded in the RFID tags, on your smart labels as a text or bar code field.

An additional EASYLABEL RFID feature is the ability to write and print a report that includes the data used to program your printed smart labels. This report can then be used as part of an ASN (Advanced Shipping Notice) or to keep a record of labelled items.

Combining all of these RFID capabilities with EASYLABEL's other time-tested features, will allow you to easily design, report, program and print smart labels.

A complimentary trial edition is available for download from Tharo's web site at www.tharo.com.

RFID Wizard for EASYLABEL labelling software - LogisticsIT.com

SMARTFORM - Font Problem Arial 12 converting to courier 12 in print

2010-03-16T11:01:00.001-07:00

how fonts in smartform works (as I guess).

A. Smartform has a smartform style
B. Smartform style use some fonts
C. In SE73 you must define font in Font families
D. In se73 you must define font as System Fonts
E. Every printer has its own Device type (LP01 has HPLJIIID I guess), so you must have in SE73 - Printer fonts - defined some of System fonts what do you want to use.
F. If the font used in smartform style is not defined in SE73 - Printer fonts - DT, SAP converts it with automatic generated table of "Font Conversion" (SE73 - Printer fonts - DT - Font Conversion Button above)
So if you dont have Arial in DT, SAP generate preview with conversion from table DT - "Font Conversion".
But beware ! It doesnt say what font will be used on printer. It says Print Controls in Device Type of Printer AND SE73 - Printer fonts - DT - Font x print control selection (or conversion table, if font doesnt exist).

Note 776507

2010-03-16T07:44:00.001-07:00

Subscribe
|
Add to Favorites

Note 776507 - SAPscript/SmartForms: Which fonts for which languages?

Note Language:
Version: 4
Validity: valid since 22.08.2005

PDF
Download Corrections
Compare Versions
SSCR

Go to SAP Note: Display

Content: Summary | Header Data | Releases | Related Notes

Summary

Symptom

Documents printed via SAPscript or SmartForms do not print with correct special characters, e.g. ### prints instead of Japanese or Russian characters. What to do?

Other terms

SAPscript, SmartForms, printing, device types, OTF

Reason and Prerequisites

Help required to choose proper fonts in a SAPscript or SmartForm

Solution

When using SAPscript or SmartForms to print (or email or fax) a form from a business application, many factors influence the outcome of the actual text within the form. All these factors must be checked in order to ensure a correct printout:
1) The language version of the form used to produce the printout.
Example: If you want to print a French invoice, you need to have a FR version of your SAPscript or SmartForms invoice form RVINVOICE01. And the application program must specify the corresponding language key (FR) when calling the SAPscript or SmartForms API.
2) The font selections specified in the form (possibly also in a SAPscript style or SmartStyle used in a form).
Example: In a SAPscript form or a SmartStyle you need to specify HELVE if you want to print German text in Helvetica (or similar) font. If you want to print Japanese text, HELVE is not a valid choice but you need to specify a Japanese font like JPMINCHO in your Japanese form.
3) The output character set of the device type
Every printer in transaction SPAD has a "device type" assigned. Device types used by the spooler for printing support only one single specific output character set. All text from the form has to be converted (using SAP's built-in character conversion mechanism) to this output character set.
A character set can typically support either a single language (e.g. Shift-JIS which supports only Japanese) or a set of languages (e.g. ISO 8859-1, which supports Western-European languages). It is possible that a given language (such as German) can be supported by several output character sets, e.g. you may use either ISO 8895-1 (Latin-1) or ISO 8859-2 (Latin-2) to represent German text. This is so because both character sets contain the special characters used in German.
Example: HPLJ4000 is a HP LaserJet device type supporting the ISO 8859-1 (Latin-1) character set. ISO 8859-1 can be used to represent e.g. Dutch, English, French, German, Spanish, Swedish but NOT Russian or Japanese.
As a consequence, it is ok to use HPLJ4000 to print English, German French etc. but not for Japanese or Russian.
4) The set of available printer fonts for a given device type
When formatting a document, SAPscript and SmartForms perform an automatic mapping of the font definitions in the form (e.g. "HELVE 14 point bold") and the available printer fonts of the device type. A replacement printer font is chosen, should the specified font selection not be available in the device type. Now this replacement can be problematic if a language-specific font, such as Chinese CNSONG, is specified in a form and it gets replaced by a font which does not support this language, e.g. COURIER.
To solve this problem, font families in SE73 have language attribute assigned, e.g. some fonts are characterized as being suitable only for certain languages. And when a replacement has to be chosen because the original font from the form is not available in the device type, a replacement font is chosen which has the same language attributes.
If no fonts for the language in question exist in the device type, the resulting font will not be able to print the special characters and you will see "wrong" output characters in the printout.
Note on SAPscript/SmartForms Print Preview:
The OTF Print Preview available in Windows GUI (e.g. from transaction SP01) will sometimes not show the "wrong" characters which appear on the final printout. Here is the reason: since the Print Preview runs in Windows environment, it will use Windows fonts to represent the actual printer fonts. A Windows font typically has more available characters (i.e. covers more character sets) than are actually available in a printer's resident font.
A typical example where the Print Preview will differ from the printout is here: if you have a Chinese PCL5 printer such as CNHPLJ4 and use the Western Latin font COURIER in your document, the print preview will show you Chinese characters if you (by accident) tried to format Chinese characters in COURIER font. This is because Windows will automatically choose a font that can output Chinese characters (which is actually not Courier). But when you print the job on an actual PCL5 printer with resident Western and Chinese fonts, the Courier font will not print any Chinese characters but Western special characters instead, because the printer's resident Courier font does not include Chinese characters.
Rule of thumb: all Asian device types (e.g. CNHPLJ4, JPHPLJ4, JPPOST, KPHPLJ4) support not only Asian fonts but also COURIER, HELVE and TIMES fonts. But these Latin fonts can only be used to print English text, not Chinese/Japanese/Korean characters.

Which fonts are suitable for a given language?
Language(s):            Font family to use in a form:
************* Latin-1 (Western Europe/Americas) *******
DE,EN,FR,ES,NL,SV       COURIER, HELVE, TIMES
                        (LETGOTH, LNPRINT)
************* Latin-2 (Central Europe) ****************
PL, CZ                  COURIER, HELVE, TIMES
************* ISO 8859-4 (Baltic) *********************
ET, LT, LV              COURIER, HELVE, TIMES
************* ISO 8859-5 (Cyrillic) *******************
BG, RU, SR, UK          COURCYR, HELVCYR, TIMECYR
************* ISO 8859-7 (Greek) **********************
EL                      COUR_I7, HELV_I7, TIME_I7
************* ISO 8859-8 (Hebrew) *********************
HE                      COURIER, HELVE, TIMES
************* ISO 8859-9 (Turkish) ********************
TR                      COURIER, HELVE, TIMES
************* Simplified Chinese **********************
ZH                      CNHEI, CNKAI, CNSONG
************* Japanese ********************************
JA                      JPMINCHO, DBMINCHO, DBGOTHIC
************* Korean **********************************
KP                      KPBATANG, KPDODUM, KPGULIM
                        KPGUNGSE, KPSAMMUL
************* Traditional Chinese *********************
ZF                      TWDPHEI, TWMING, TWSONG
************* Thai ************************************
TH                      THANGSAN, THDRAFT, THVIJIT
************* Arabic (Unicode systems only) ***********
AR                      ANDALE_J

Verify your output by examining the OTF data
When analysing printing problems of this type, be sure to check the OTF data which gets produced by SAPscript or SmartForms. OTF or "Output Text Format" is the intermediate page-description format generated from SAPscript or SmartForms. OTF will contain the final printer font names and character set/language identifiers which help to solve the problem. OTF will even name the form and the language of the form used to create the output.
The easiest way to do this is to create a spool request from your application, run transaction SP01, use menu
Goto->Display Requests->Settings
and choose
Display Mode: Raw
Now display your spool request. If this is a SAPscript or SmartForms spool request, you will see OTF data. Each line represents one OTF command, every command starts with a 2-character cmd identifier and possibly some cmd parameters follow.
Here is an excerpt from a sample OTF file where we highlight the most interesting commands:
//XHPLJ8000    0700 00000+00000+1
IN04EALEXTEST_ZEBRA
IN05%PAGE1
OPDINA4 P 144 240 1683811906000010000100001
IN06%WINDOW2
MT0024401289
CP11000000E
FCHELVE 120 00109XSF100SF101110000067E X
UL +0000000000000
SW00067
CT00000000
ST0453037Dieses SF hat Stil ALEXTEST_ZEBRA mit
...
The 1st line with the // (Control) command reveals the device type used to print: HPLJ8000
//XHPLJ8000    0700 00000+00000+1
The 2nd line (IN = Info command) shows the name and (internal 1-char) language key of the form:
IN04EALEXTEST_ZEBRA
In this case it is the English (E = EN) SmartForm ALEXTEST_ZEBRA
The OP-line (OP = Open Page) gives the page format used in the form, it is DINA4 Portrait orientation:
OPDINA4 P 144 240 1683811906000010000100001
The CP (CodePage) cmd shows the SAP system codepage used to code the text and the active language. In our case it is codepage 1100 and language E = EN = English.
CP11000000E
Finally, the FC-cmd (Font Call) lists a printer font selected within SmartForms. Please note that every SmartForm has a designated default SmartStyle under "Form Attributes->Output Options". In addition, every text node can have a SmartStyle attached (which will override the definitions from the default style for the text). In our case the resulting printer font that was selected is HELVE 12.0 pt bold-off, italic-off.
FCHELVE   120 00109XSF100SF101110000067E X

Header Data

Release Status:
Released for Customer

Released on:
22.08.2005 09:57:20

Master Language:
English

Priority:
Recommendations/additional info

Category:
Customizing

Primary Component:
BC-CCM-PRN Print and Output Management

Secondary Components:
BC-SRV-SCR SAPscript

BC-SRV-SSF Smart Forms

Affected Releases

Release-Independent

Related Notes

1319517 - Unicode Collection Note

880490 - Russian Sapscript forms print with wrong characters

423003 - Printers and Asian/Eastern European fonts/languages

Print Selected Notes (PDF)

SAP Community Network Wiki - ABAP Development - Handling Idoc Acknowledgements

2010-03-16T04:34:00.001-07:00

My Home > ABAP Development > ...Data Transfers - BAPI, BDC, ALE, LSMW, DX-WB > ALE,IDOC > Handling Idoc Acknowledgements

Handling Idoc Acknowledgements
Apr 13, 2009 (view change)

Labels:

idoc, ack, acknowledgement, status

Way of handling the acknowledgements forthe custom generated Idocs.

Note: I took an example custom Idoc which has already been developed to explain the concept of handling Acknowledgements. I am providing the necessary details here before proceeding to the actual concept

Sender System       : BANGSEND
Recieving System : HYDRECIEVE
Message Type         : ZEMP84364_MNT_RPT
Basic Type                : ZEMP84364_MNT_RPT01
Functionality of the Idoc : Transfers the records created with the help of a report program and updates the database table of the target system.

For this scenaio, now we are going to see how we can handle the acknowledgement.

ALE Configuration for Idoc Acknowledgement:

Sender creates an Outbound Idoc and this particular Idoc is received by the receiver as an Inbound Idoc and receiver system processes the Idoc, it updates the database tables. Now, Sender system would never know what happened to the document that it has passed to the receiver. So, to make sure that the receiver had posted the application document in the necessary database tables, we would need an Acknowledgement.

ALEAUD is a standard message type through which we can achieve this functionality. Now, we need to update the settings for ALEAUD message type in both sender and receiver systems.

Add ALEAUD message type in the outbound parameters for the partner BANGSEND. Now, this particular Ack Idoc would behave as an outbound Idoc from the receiver system of the actual Idoc to the sender system of the actual Idoc.

The settings after adding the ALEAUD Idoc in the outbound parameters in the above screen is shown below.
This is the place where we are using the port that we have created in the receiver system.
Note: Select the Output mode as Transfer Idoc immediately (Though it is optional, you can collect all the Idocs and process them using a job). Save the screen.
Now, make similar settings in the sender system. As, HYDRECIEVE is the partner for the BANGSEND system, you would receive the Acknowledgement Idoc as inbound in the BANGSEND system. So, add the ALEAUD message type in the Inbound parameters of the partner HYDRECIEVE as shown below.
The actual process code settings that we need to do after adding the message type ALEAUD in the inbound parameters is shown below
Since you are using the standard message type, no need to write a function module to process these Ack Idocs. Even the process code that we are using is a standard one.
Now, you need to create Distribution model in the receiver system for these ALEAUD Idocs
Below screen shows that, HYDRECIEVE system is going send ALEAUD Idocs to the BANGSEND system with the distribution model name MODEL_ACKS which we have not yet created.

Save the screen now which is very important

To generate partner profiles, go to the menu Environment and click on Generate Partner Profiles and execute the below screen.

After executing the above screen you would see that the partner profiles created. Items marked in the green color are the ones which are created automatically.
A standard message type SYNCH always gets generated and you can check the same in the partner profiles.

Now, once you are done with the above you need to distribute the distribution model with the partner system by clicking on the menu Edit -> Model View -> Distribute
Click on Ok and the distribution model is shared with the partner system as shown in the next screen.

Click on OK.

Testing the Idoc by running the Application Program:

Go to the Sender system, execute the Application Program (ABAP Program) and enter the selection screen the details as shown below.

Now execute the above screen and you would see the output saying the Idoc number generated as shown below

Now, Go to WE05 transaction and see the above Idoc.
In the above screen the very last one is the Idoc that has been created now. Let us open the Idoc and verify the contents as shown below.

In the above screen, the final status of the Idoc is 03. It means that, the Idoc has gone to the destination system. But, we do not know whether the Idoc has been processed there or not. Now, let us go to the target system and check whether this particular Idoc has been converted in to an Inbound Idoc to get posted in the target database.
Execute WE05 transaction in the target system and see the Idoc. Based on the time, the last Idoc that has been processed should be the Idoc that has been created. The Idoc is selected for the reference.

Let us open the Idoc and see whether the contents of the Outbound Idoc of Sender are same as the contents of the Inbound Idoc in the target system.

You can see that content of the Idoc is same and as the status of the Idoc is in 53, we can confirm that the Idoc has been posted in the target database.
Let us verify that by opening the database table in the target system.

We can see that the record has been updated in the target database.

This ends the Idoc posting.

But, in the view of Sender as the Outbound Idoc is in 03 status, Sender would never know what happened to the Idoc in the target system.
So, in production environment generally a job is set to run periodically which has the program RBDSATATE with the variant SAP_AUDIT_SEND to send the audit data back to the Sender from the target system.

In our case, let us run the job manually to send the Audit data back to the sender system

The job has finished and the spool shows that there is an Idoc with the message type ALEAUD that has been generated as shown below.

Now, go to the Sender system and check the status of the Idoc it should have been changed to 41(Final Status of any Outbound Idoc) as the Idoc has been posted successfully here in the target system.Go to sender system and open WE05 transaction.

In the above screen, you can clearly see that all the Idocs have been changed to the status 41. You can see the same for our Idoc in the below screen.

This ends the way of handling Idoc Acknowledgements.

Contact Us Site Index Marketing Opportunities Legal Terms Privacy Impressum
Powered by SAP NetWeaver

SAP Community Network Wiki - ABAP Development - Handling Idoc Acknowledgements

SAP Community Network Wiki - ABAP Development - ALE,IDOC

2010-03-16T04:22:00.001-07:00

ALE Technology : Application Link Enabling (ALE) is a technology to create and run distributed applications. ALE Technology is proprietary of SAP.

ALE Objectives - ALE incorporates controlled exchange of data messages ensuring data consistency across loosely coupled applications. ALE comprises of three layers. Application Services Distribution Services and Communication Services .Basic principle of ALE is to provide a distributed and fully integrated R/3 system. Each application is self-sufficient. The use of self-sufficient system implies a certain measure of data redundancy.Hence data has to be both distributed and synchronized.

Difference Between ALE and EDI :Normally we refer to EDI technology when a non SAP system is one of the communication channel. ALE communication occurs from the SAP side and EDI from the non-SAP side. IDOCs uses ALE and EDI to deliver the data to the receiving system. If the data needs to be exchanged between two SAP systems, then IDOC uses ALE technology . For the exchange of data between a SAP and Non SAP system, IDOC uses EDI subsystem to convert and deliver the data.

ALE Communication Diagram

1. What is the difference Between IDOC type and Message type? How to link the IDOC type with Message type?
Message type gives the meaning of the IDOC . IDOC type gives the structure of an IDOC.The messages exchanged between systems are of various message types. The message type depends on the data contained and the process involved. It determines the technical structure of the message and the IDOC type.The IDoc type indicates the SAP format that is to be used to interpret the data of a business transaction.
In the OO(Object Oriented) approach, Message Type can be refferred to a Class and IDOC Type as an instance of the class Message Type
The linkage will happen in transaction WE82.

2. Where the IDOC information gets stored?

Table
Description

EDIDC
Stores the Control Record information an IDOC

EDID4
Stores the Data Records (version 4.6)

EDIDD
Data Seg (EDI Intermediate doc)

EDIDS
Stores the Status of an IDOC

3. What is process code? What are type of process codes

Process code refers to an workflow or a function module which helps in reading or writing data from/to Idoc. Process Codes are used in both ALE and EDI framework to identify the function module or API (Application Programming Interface) to be invoked for subsequent processing. Inbound as well as outbound interfaces use process code but for different purposes. Outbound process codes are stored in table TEDE1, while inbound process codes are stored in TEDE2.

Following are types of process code

Process Code
Description

Outbound Process Code
This will read application data and place data in Idoc

Inbound Process Code
This will Idoc and create corresponding application data

System Process Code
This will create work item in case some error occurs in idoc / application document processing

Status Proces Code
This will handle error that occurs when a idoc is sent to some other system

4. How to reprocess an IDOC?

You can use the below Programs for IDocs Reprocessing:

RBDMANI2 : Reprocess Idocs manually

RBDMANIN : Posting of IDocs with Status 51

RBDMOIND : Outbound Idocs status 03->12

RSEOUT00 : For Processing 30 Status IDocs

RBDAPP01 : For Processing 64 Status IDocs

RBDAGAIN : Reprocess Incorrect Outbound IDocs

RBDAGAI2 : Reprocessing of IDocs after ALE Input Error

5. How to trace the IDocs of the Receiving system from the Sending system?

Steps:

Execute the transaction BD87

Give the Outbound IDocs in the IDoc Number field and execute or Just Note the Start time and End time when u execute the Master Data Transaction say for eg.BD10 and specify the same in the Time Created input field of BD87,also give the Message Type and the Receiving System Names and execute.

Select the Repective Message Type and Press the Trace IDoc Button.

6. How to trace IDocs based on the data .

Steps:

Execute Transaction WE09

Put in the message type name in the field labeled 'Logical Message' Ex - DEBMAS

Now we will move to the section 'Criteria for Search in Data Records '

In this section we will put the Segment name in which we want to search the existance of data in the field labeled 'Search in Segment' EX - E1KNA1M

In the field labeled 'Search in Field' we will put the field name of the segment in which we want to search the existance of data. Ex - KUNNR for searching IDOCs for certain customer number.

Now in the field labeled 'For Value' we will put the search value. Ex - Customer number as 100 .

We will now execute the transaction.

The result can be a single Idoc or a list of multiple IDOCS depending upon the Search Criteria entered.

7. How to Send and Receive an IDoc in the same system.

Steps :

Create a Dummy Logical System.

Goto T-Code SALE-> sending and Receiving Systems -> Logical Systems -> New entries.Enter SYSID_CLNT, but this one is Dummy so use the first 2 characters of the SYSID and prefix 'D' then underscore and then the Client number.

E.g.: If ERP_100 is the logical system of the R/3 then create ERD_100 as the dummy system.

Create Port for the Original System, (ERP_100)

Goto WE21 and select Transactional Port and press the Create button. Name the Port as "SAP" contatenated with the SYSID in our example it would be SAPERP Select the appropriate version and enter the RFC dest of the system that you are working on in this case it will be 'ERP'.

Create Partner Profile in partner type LS:

Receiver Side ( Outbound to ) : In Partner type LS name ERD_100create the Outbound Parameters, give the Message type, Receiver Port same as the port we created in step 2. Enter the Basic type.

Sender Side ( Inbound From ): In partner type LS name ERP_100 create the Inbound Parameters, give the appropriate message type and the process code.

Now create the stand alone program to send the IDoc:

The program will at some point calls the MASTER_IDOC_DISTRIBUTE function module. When you pass the EDIDC structure it will be populated as follows:
i_edidc-mestyp = message type.
i_edidc-idoctp = basic type.
i_edidc-rcvprt = 'LS'.
Concatenate 'SAP' sy-sysid into l_port.
i_edidc-RCVPOR = l_port.
i_edidc-rcvprn = 'ERD_000'.
CONCATENATE sy-sysid '_' sy-mandt
INTO l_sndprn.
i_edidc-SNDPRN = l_sndprn.
i_edidc-sndprt = 'LS'.
i_edidc-sndpor = l_port.

Observe that the Sender port and the receiver port is the same, this does the trick. The outbound Idoc is sent on the port SAPERP with the Sender as ERP_100 and receiver as ERD_100 and then the Inbound Idoc is also sent to the same port SAPERP with the Sender as ERP_100 and receiver as ERD_100.

8. What is message control and when do we use it?

Message control is a mechanism by which documents are output based on a selection criteria and requirements. This concept is applicable not only to EDI and ALE, but also to other output mediums (for example: print, fax). Message control determines the type of document, its timing, number, and the medium. NAST table stores output records. The conditions (selection criteria and requirements) for creating an output message are stored in condition tables. Search mechanisms are used through access sequences, output processes, and requirements to determine whether an application document qualifies for output.

Some of the tables for Message Control are :

Transaction Code
Description

NACE
Condition Record Maintenance

VOK2
SD Message Control Components

VOK3
Purchasing message Control Components

VOFM
View Message Requirements

V/86
Condition Table Field Catalog

WE15
IDOC test : outbound from Message Control

9. How do you reprocess the failed trfc entries?

You can reprocess the failed trfc entries using the program RSARFCEX.

10. What is the transaction used to find the outbound and inbound process codes at one place?

WE64

Children Hide Children | View in Hierarchy

7 Steps For ALE Configuration
Administration of ALE Functions and Troubleshooting ALE
ALE- DDIC tables that are reflected with respect to Partner Profiles
Change Pointers
Creating an ABAP program from a BDC recording
Customer Master Record (Tax Groupings) in Customer ALE
EDI 997 - Functional acknowledgement
Handling Idoc Acknowledgements
IDOC Steps
Idocs
Interface Development using IDOC's
Managing Data in different Formats with IDOC
Message Control for ALE
Modify IDOC Status by Program
Outbound Idoc Through ALE
TO BE DELETED

SAP Community Network Wiki - ABAP Development - ALE,IDOC

FU BAPI_INCOMINGINVOICE_CREATE

2010-03-14T08:44:00.001-07:00

___________________________________________________
Short Text
Invoice Verification: Post Invoice

Functionality
You can use this method to create and post incoming invoices.

When passing on the header data, you use the INVOIC_IND field to determine whether the system posts a credit memo or an invoice. If you leave the field initial, the system posts a credit memo. If you enter an X, the system posts an invoice.

If you want to enter an invoice for a returns order, you must leave the INVOICE_IND field initial.

As in the online transaction, the system updates the purchase order history and stock valuation data in Materials Management. The system creates accounting documents in Accounting.

You can use this method to:

Enter and post invoices with multiple account assignment
Change the account assignment of invoices, add account assignments, and post the invoices
Enter invoices for blanket purchase orders
Enter and post invoices for purchase orders containing planned delivery costs
Enter and post invoices containing unplanned delivery costs
Enter and post subsequent debits/credits
Use document types with external number assignment
Enter and post invoices with withholding tax
Enter and post invoice with more than one vendor line and different payment methods and terms of payment
Enter and post invoices for returns orders
Enter and post invoices for transportation service providers
Enter and post invoices for external service orders
Post to G/L accounts
Post to material accounts
Enter and post invoices for a one-time vendor
Enter and post invoices with a different payee
Restrictions

The following fields in Financial Accounting are not passed on:

ISR number (ISR = inpayment slip with reference number)
Bank details
Payment reference
House bank ID
Notes
The following authorization object is checked using activity 01:

M_RECH_WRK: Authorization to create invoices in certain plants
Transfer

You use the structure HeaderData to pass on the header data of the incoming invoice.

You pass on the address data of a one-time vendor or a different invoice payee with the structure AddressData.

Tables ItemData and AccountingData contain the invoice item data. The table TaxData contains the tax information for the invoice.

The tables ItemData and AccountingData contain the item data of the incoming invoice. The TaxData table contains the tax information on the invoice.

The table GlAccountData contains data for posting to a G/L account and the MaterialData table contains data for posting to a material account.

You can use the table WithTaxData to pass on withholding tax information.

Via the table VendorItemSplitData, you can distribute the gross amount among several creditor lines with different payment methods and terms of payment.

Return

The document number of the invoice document and the fiscal year are returned by the system as key fields of the incoming invoice.

Return messages

Messages are returned in the Return parameter. The parameter documentation shows the return codes and their meanings.

Further information
The method can only perform your function if no error messages were generated in the Return table. This is the case if the header data and all the items were processed successfully.

Transaction control is not implemented. The calling program therefore has to execute the Commit Work itself after this method has been successfully invoked (in other words, if no errors were reported in the Return parameter).

Example: Incoming Invoice
This example shows the header data that you need to enter in table Headerdata and the item data that you need to enter in table Itemdata to post an invoice.

Purchase order: 10 pc of material A @ $10/pc
Goods receipt: 10 pc of material A

You receive an invoice against this purchase order referencing PO number 4500007491, PO item 10, for a quantity of 10 pc of material A and an amount of $116, including 16% VAT. Enter the following data:

HeaderData table

INVOICE_IND (Post invoice/credit memo): X
DOC_DATE (Document date): 05.20.2000
PSTNG_DATE (Posting date): 05.23.2000
COMP_CODE (Company code): 1000
GROSS_AMOUNT (Gross amount): 116.00
CURRENCY (Currency key): USD
CALC_TAX_IND (Calculate tax): X
ItemData table

INVOICE_DOC_ITEM (Invoice document item): 00001
PO_NUMBER (Purchase order number): 4500007491
PO_ITEM (Purchase order item): 00010
TAX_CODE (Tax code): VN
ITEM_AMOUNT (Item amount): 100
QUANTITY (Quantity): 10
PO_UNIT (Unit of measure): PC
For more information, see the parameter documentation for tables HeaderData and Itemdata.

Example: Incoming invoice in foreign currency, goods-receipt-based invoice verification and tax information
This example specifies the header data that you need to enter in table Headerdata, the item data that you need to enter in table Itemdata and the tax information that you need to enter in table TaxData to post an invoice in a foreign currency.

Purchase order: 10 pc of material A @ $10/pc
First goods receipt: 4 pc of material A
Second goods receipt: 6 pc of material A

You receive an invoice against this purchase order referencing PO number 4500007505, PO item 10, goods receipt document 50010095, 2000, item 1. The invoice is for a quantity of 4 pc of material A, a gross amount of $46.60 and 16% tax ($6.60). Enter the following data:

HeaderData table

INVOICE_IND (Post invoice/credit memo): X
DOC_DATE (Document date): 05.20.2000
PSTNG_DATE (Posting date): 05.23.2000
COMP_CODE (Company code): 1000
CURRENCY (Currency key): USD
GROSS_AMOUNT (Gross amount): 46.60
ItemData table

INVOICE_DOC_ITEM (Invoice document item): 00001
PO_NUMBER (Purchase order number): 4500007505
PO_ITEM (Purchase order item): 00010
REF_DOC (Goods receipt document): 50010095
REF_DOC_YEAR (Fiscal year of current period): 2000
REF_DOC_ITEM (Goods receipt document item): 1
TAX_CODE (Tax code): VN
ITEM_AMOUNT (Item amount): 40.00
QUANTITY (Quantity): 4
PO_UNIT (Unit of measure): PC
TaxData table

TAX_CODE (Tax code): VN
TAX_AMOUNT (Tax amount in document currency): USD 6.60
For more information, see the parameter documentation for tables HeaderData, ItemData, and TaxData.

Example: Incoming invoice for blanket purchase order
This invoice shows which header data you need to enter in the table HeaderData, which item data you need to enter in the table ItemData, and which account assignment data you need to enter in table AccountingData to post an incoming invoice for a blanket purchase order.

You receive an invoice in respect of the blanket purchase order 4500015172, item 10 for an amount of $110 including 10% VAT. You want to apportion the invoice amount to the cost centers 1200 and 1500. Enter the following data:

HeaderData table

INVOICE_IND (Post invoice/credit memo): X
DOC_DATE (Document date): 02.19.2001
PSTING_DATE (Posting date): 02.21.2001
COMP_CODE (Company code): 1000
GROSS_AMOUNT (Gross amount): 110
CURRENCY (Currency): USD
CALC_TAX_IND (Calculate tax): X
ItemData table

INVOICE_DOC_ITEM (Item in the invoice document): 00001
PO_NUMBER (PO number): 4500015172
PO_ITEM (PO item): 00010
TAX_CODE (Tax code): V1
ITEM_AMOUNT (Item amount): 100
AccountingData table

1st line: Change account assignment data

INVOICE_DOC_ITEM (Document item in invoice document): 0001
SERIAL_NO (Serial number for the accont assignment): 01
TAX_CODE (Tax code): V1
ITEM_AMOUNT (Amount in document currency): 30
GL_ACCOUNT (G/L account number): 890000
COSTCENTER (Cost center): 1200
2nd line: Add unplanned account assignment

INVOICE_DOC_ITEM (Document item in invoice document): 0001
XUNPL (Unplanned acct. assignment from IV): X
TAX_CODE (Tax code): V1
ITEM_AMOUNT (Amount in document currency): 70
GL_ACCOUNT (G/L account number): 890000
COSTCENTER (Cost center): 1500
In the case of the blanket purchase order, the following fields for quantities and units of measure must not be populated in the tables ItemData and AccountingDataAccountingData:

Quantity (QUANTITY)
PO_UNIT (PO unit of measure)
PO_UNIT_ISO (PO unit of measure in ISO code)
PO_PR_QNT (Quantity in PO price unit of measure)
PO_PR_UOM (PO price unit of measure)
PO_PR_UOM_ISO (PO price unit of measure in ISO code)
More information is available in the parameter documentation for the tables HeaderData, ItemData, and AccountingData, and in the SAP Library under Logistics Invoice Verification.

Example: Change account assignments and add unplanned assignments
This example shows the header data that you need to enter in table Headerdata, the item data that you need to enter in table Itemdata, and the account assignment information that you need to enter in table AccountingData to change, add, and post account assignments for an invoice. If you want to change or add account assignments, there must be a non-valuated goods receipt or no goods receipt in the system. Goods-receipt-based invoice verification is specified.

Purchase order: 300 pc of material A @ $1.00/pc
Goods receipt: 300 pc of material A

This purchase order is subject to account assignment. You receive an invoice for it, referencing the PO number 4500006846, PO item 10, goods receipt document 50008849, 2000, item 1. The invoice is for a quantity of 100 pieces of material A, with a gross invoice amount of USD 116.00, including 16% VAT. You want to change the planned account assignment for the second account assignment item and add an unplanned account assignment. Enter the following data:

HeaderData table

INVOICE_IND (Post invoice/credit memo): X
DOC_DATE (Document date): 08.05.2000
PSTNG_DATE (Posting date): 08.08.2000
COMP_CODE (Company code): 1000
CURRENCY (Currency key): USD
GROSS_AMOUNT (Gross amount): 17.40
CALC_TAX_IND (Calculate tax automatically): X
PMNTTRMS (Terms of payment key): 0001
ItemData table

INVOICE_DOC_ITEM (Invoice document item): 00001
PO_NUMBER (Purchase order number): 4500006846
PO_ITEM (Purchase order item): 00010
REF_DOC (Goods receipt document): 500008849
REF_DOC_YEAR (Fiscal year of current period): 2000
REF_DOC_ITEM (Goods receipt document item): 1
TAX_CODE (Tax code): VN
ITEM_AMOUNT (Item amount): 100
QUANTITY (Quantity): 100
PO_UNIT (Unit of measure): PC
AccountingData table

Line 1: Change second account assignment item

INVOICE_DOC_ITEM (Invoice document item): 0001
SERIAL_NO (Account assignment serial number): 02
TAX_CODE (Tax code): VN
ITEM_AMOUNT (Amount in document currency): 10.00
QUANTITY (Quantity): 10
PO_UNIT (Order unit): PC
GL_ACCOUNT (G/L account number): 890000
COSTCENTER (Cost center): 1200
Line 2: Add unplanned account assignment

INVOICE_DOC_ITEM (Invoice document item): 0001
XUNPL (Unplanned account assignment in Invoice Verification): X
TAX_CODE (Tax code): VN
ITEM_AMOUNT (Amount in document currency): 5.00
QUANTITY (Quantity): 5
PO_UNIT (Order unit): PC
GL_ACCOUNT (G/L account number): 890000
COSTCENTER (Cost center): 1200
More information is available in the parameter documentation for the tables HeaderData, ItemData, and AccountingData and in the SAP Library under Logistics Invoice Verification.

Example: Incoming invoice with planned delivery costs
This examples shows the header data that you need to enter in table HeaderData, the item data that you need to enter in table ItemData, and the tax information that you need to enter in table TaxData to post an invoice containing planned delivery costs.

Purchase order: 100 pc of material A @ $1.00/pc
Goods receipt: 100 pc of material A

You receive an invoice for this purchase order referencing PO number 4500006986, PO item 10, for a quantity of 100 pieces of material A and $136.00, including 16% VAT and $20.00 planned delivery costs. Enter the following data:

HeaderData table

INVOICE_IND (Post invoice/credit memo): X
DOC_DATE (Document date): 08.10.2000
PSTNG_DATE (Posting date): 08.12.2000
COMP_CODE (Company code): 1000
CURRENCY (Currency key): USD
GROSS_AMOUNT (Gross amount): 136,00
ItemData table

Line 1: Posting the purchase order item

INVOICE_DOC_ITEM (Invoice document item): 00001
PO_NUMBER (Purchase order number): 4500006986
PO_ITEM (Order item): 00010
TAX_CODE (Tax code): VN
ITEM_AMOUNT (Item amount): 100.00
QUANTITY (Quantity): 100
PO_UNIT (Unit of measure): PC
Line 2: Posting the planned delivery costs

INVOICE_DOC_ITEM (Invoice document item): 00002
PO_NUMBER (Order number): 4500006986
PO_ITEM (Order item): 00010
ITEM_AMOUNT (Item amount): 20.00
QUANTITY (Quantity): 100
PO_UNIT (Unit of measure): PC
COND_TYPE (Condition type): FRB1
TaxData table

TAX_CODE (Tax code): VN
TAX_AMOUNT (Tax amount in document currency): 16.00
For more information, see the parameter documentation for tables HeaderData, ItemData, and TaxData.

Example: Incoming invoice with withholding tax
This example shows which header data you can enter in the table HeaderData, which item data you can enter in the table Itemdata, and which withholding tax information you can enter in the table WithTaxData in order to park an incoming invoice with withholding tax.

Purchase order: 10 pc of material A @ $10

Goods receipt: 10 pc of material A

You receive an invoice for this purchase order referencing PO number 4500007505, PO item 10, GR document 50010095 2000, item 1. The invoice is for a quantity of 10 pc and a gross amount of $100. You have to pay 10% withholding tax on the gross amount. Enter the following data:

HeaderData table

INVOICE_IND (Invoice/Credit memo): X
DOC_DATE (Document date): 05.20.2000
PSTNG_DATE (Posting date): 05.23.2000
COMP_CODE (Company code): WT01
CURRENCY (Currency key): USD
GROSS_AMOUNT (Gross amount): $100
ItemData table

INVOICE_DOC_ITEM (Item from invoice document): 00001
PO_NUMBER (PO number): 4500007505
PO_ITEM (PO item): 00010
REF_DOC (GR document): 50010095
REF_DOC_YEAR (Fiscal year of the current period): 2000
REF_DOC_ITEM (Item in a GR document): 1
TAX_CODE (Tax code): V0
ITEM_AMOUNT (Item amount): $100
QUANTITY (Quantity): 10
PO_UNIT (Unit of measure): PC
WithTaxData table

SPLIT_KEY (Grouping key for withholding tax split): 0001
WI_TAX_TYPE (Code for withholding tax type): R1
WI_TAX_CODE (Withholding tax code): 01
WI_TAX_BASE (Withholding tax base amount): 100
WI_TAX_AMT (Withholding tax amount in doc. currency): 10.00
For more information, see the parameter documentation for the tables HeaderData, ItemData, and WithTaxData.

Example: Incoming invoice with amount split
This example shows you which header data you can enter in the HeaderData table, which item data you can enter in the Itemdata table, and which information you can enter in the VendorItemSplitData table to create an incoming invoice with amount split.

Purchase order: 10 pc of material A @ $10

Goods receipt: 10 pc of material A

You receive an invoice for this purchase order referencing PO number 4500007505, PO item 10, GR document 50010095, item 1. The invoice is for a quantity of 10 pieces and a gross amount of $100. You want to apportion the gross amount to two creditor lines. 40% of the gross amount is to be paid immediately by check, and 60% of the gross amount is to be paid within 14 days, taking into account a 3% cash discount. Enter the following data:

HeaderData table

INVOICE_IND (Invoice/Credit memo): X
DOC_DATE (Document date): 05.20.2000
PSTNG_DATE (Posting date): 05.23.2000
COMP_CODE (Company code): 0001
CURRENCY (Currency key): USD
GROSS_AMOUNT (Gross amount): 100.00
ItemData table

INVOICE_DOC_ITEM (Item from the invoice document): 00001
PO_NUMBER (PO number): 4500007505
PO_ITEM (PO item): 00010
REF_DOC (GR document): 50010095
REF_DOC_YEAR (Fiscal year for the current period): 2000
REF_DOC_ITEM (Item from a GR document): 1
TAX_CODE (Tax code): V0
ITEM_AMOUNT (Item amount): 100
QUANTITY (Quantity): 10.00
PO_UNIT (Unit of measure): PC
VendorItemSplitData table

1st creditor line

SPLIT_KEY (Grouping key for split in the vendor line): 0001
SPLIT_AMOUNT (Gross invoice partial amount in doc. currency): 40.00
PYMT_METH (Payment method): S
TAX_CODE (Tax code): V0
PMNTTRMS (Payment terms key): 0001
2nd creditor line

SPLIT_KEY (Grouping key for split in the vendor line): 0002
SPLIT_AMOUNT (Gross invoice partial amount in doc. currency): 60.00
PYMT_METH (Payment method): U
TAX_CODE (Tax code): V0
PMNTTRMS (Payment terms key): 0003
For more information, see the parameter documentation for tables HeaderData, ItemData, and VendorItemSplitData.

Example: Incoming Invoice with G/L and Material Account Posting
This example shows you which data you have to provide in order to enter and post an incoming invoice (header data in table HeaderData, item data in table ItemData, G/L account information in table GlAccountData, and material account information in table MaterialData).

You receive an invoice with reference to PO number 4500006846, PO item 10. The invoice is for a quantity of 100 PC of material A, a gross amount of 150.80 USD incl. 16% tax. Included in this is a G/L account posting of 10 USD to account 400000 in company code 1, and a material account posting to the material MAT01n for 20 USD.

Enter the following data:

HeaderData table

INVOICE_IND (Post invoice/credit memo): X
DOC_DATE (Document date): 08.05.2000
PSTNG_DATE (Posting date): 08.08.2000
COMP_CODE (Company code): 1000
CURRENCY (Currency key): USD
GROSS_AMOUNT (Gross amount): 150.80
CALC_TAX_IND (Automatically calculate tax): X
PMNTTRMS (Payment terms key): 0001
ItemData table

INVOICE_DOC_ITEM (Invoice document item): 00001
PO_NUMBER (PO number): 4500006846
PO_ITEM (PO item): 00010
TAX_CODE (Tax code): VN
ITEM_AMOUNT (Item amount): 100
QUANTITY (Quantity): 100
PO_UNIT (Unit of measure): PC
GlAccountData table

INVOICE_DOC_ITEM (Document item in invoice document): 00001
GL_ACCOUNT (G/L account): 400000
ITEM_AMOUNT (Item amount): 10,00
DB_CR_IND (Debit/credit indicator): S
COMP_CODE (Company code): 0001
TAX_CODE (Tax code): VN
COSTCENTER (Cost center): 1
MaterialData table

INVOICE_DOC_ITEM (Document item in invoice document): 0001
MATERIAL (Material): MAT01
PLANT (Valuation area): 0001
DB_CR_INP (Debit/credit indicator): S
ITEM_AMOUNT (Item amount): 10.00
QUANTITY (MENGE_D): 1
PO_UNIT (PO quantity unit of measure): PC
TAX_CODE (Tax code): VN
More information is available in the parameter documentation for the tables HeaderData, ItemData, GlAccountData and MaterialData and in the SAP Library under Logistics Invoice Verification.

Example: Invoice for a purchase order for external services and service-based invoice verification
This example shows you which header data you must enter in the table HeaderData, which item data you must enter in the table ItemData, and which account assignment data you must enter in the table AccountingData in order to enter and post an incoming invoice.

You receive an invoice referencing PO number 4500000191, PO item 10. Two services, A and B, are invoiced, each with a quantity of six service units. Service A has a gross amount of 580 euros incl. 16% VAT. Service B has 812 euros incl. 16% VAT. Service A has an account assignment of 50% to each of the two cost centers 1000 and 2000. Service B also has a 50-50 account assignment, to cost centers 1000 and 3000. The service acceptance is performed jointly for both services in one service entry sheet, number 1000000022. You cannot change the account assignments. Enter the following data:

HeaderData table

INVOICE_IND (Post invoice/credit memo): X
DOC_TYPE (Document type): RE
DOC_DATE (Document date): 01.10.2002
PSTNG_DATE (Posting date): 01.10.2002
COMP_CODE (Company code): 0001
CURRENCY (Currency key): USD
GROSS_AMOUNT (Gross amount): 1392.00
CALC_TAX_IND (Calculate tax automatically): X
PMNTTRMS (Payment terms key): 0001
ItemData table

First entry for service A:

INVOICE_DOC_ITEM (Item in invoice document): 000001
PO_NUMBER (PO number): 4500000191
PO_ITEM (PO item): 00010
TAX_CODE (Tax code): V1
ITEM_AMOUNT (Item amount): 250.00
QUANTITY (Quantity): 1
PO_UNIT (Unit of measure): SU
SHEET_NO (Service entry sheet number): 1000000022
SHEET_ITEM (Line number): 10
Second entry for service A:

INVOICE_DOC_ITEM (Item in invoice document): 000002
PO_NUMBER (PO number): 4500000191
PO_ITEM (PO item): 00010
TAX_CODE (Tax code): V1
ITEM_AMOUNT (Item amount): 250.00
QUANTITY (Quantity): 3
PO_UNIT (Unit of measure): SU
SHEET_NO (Entry sheet number): 1000000022
SHEET_ITEM (Line number) : 10
First entry for service B:

INVOICE_DOC_ITEM (Item in invoice document): 000003
PO_NUMBER (PO number): 4500000191
PO_ITEM (PO item): 00010
TAX_CODE (Tax code): V1
ITEM_AMOUNT (Item amount): 350.00
QUANTITY (Quantity): 3
PO_UNIT (Unit of measure): SU
SHEET_NO (Entry sheet number): 1000000022
SHEET_ITEM (Line number) : 20
Second entry for service B:

INVOICE_DOC_ITEM (Item in invoice document): 000004
PO_NUMBER (PO number): 4500000191
PO_ITEM (PO item): 00010
TAX_CODE (Tax code): V1
ITEM_AMOUNT (Item amount): 700.00
QUANTITY (Quantity): 1
PO_UNIT (Unit of measure): SU
SHEET_NO (Service entry sheet number): 1000000022
SHEET_ITEM (Line number) : 20
AccountingData table

First account assignment for service A:

INVOICE_DOC_ITEM (Document item in invoice document): 000001
SERIAL_NO (Sequential number of the account assignment): 01
TAX_CODE (Tax code): V1
ITEM_AMOUNT (Amount in document currency): 250.00
QUANTITY (Quantity): 3
PO_UNIT (PO unit of measure): SU
Second account assignment for service A:

INVOICE_DOC_ITEM (Document item in invoice document): 000001
SERIAL_NO (Sequential number of the account assignment): 02
TAX_CODE (Tax code): V1
ITEM_AMOUNT (Amount in document currency): 250.00
QUANTITY Quantity): 3
PO_UNIT (PO unit of measure): SU
First account assignment for service B:

INVOICE_DOC_ITEM (Document item in invoice document): 000003
SERIAL_NO (Sequential number of the account assignment): 01
TAX_CODE (Tax code): V1
ITEM_AMOUNT (Amount in document currency): 350.00
QUANTITY (Quantity): 3
PO_UNIT (PO unit of measure): SU
Second account assignment for service B:

INVOICE_DOC_ITEM (Document item in invoice document): 000004
SERIAL_NO (Sequential number of the account assignment): 03
TAX_CODE (Tax code): V1
ITEM_AMOUNT (Amount in document currency): 350.00
QUANTITY (Quantity): 3
PO_UNIT (PO unit of measure): SU
More information is available in the parameter documentation for the tables HeaderData, ItemData, and AccountingData, and in the SAP Library under Logistics Invoice Verification.

Example: Incoming invoice for one-time vendor
This example shows you how to proceed in order to enter and post an invoice for a one-time vendor.

You do not need to enter data in the AddressData table. If you do not enter data in the AddressData table, the address data for the one-time vendor is adopted 1:1 in the invoice from the purchase order.

If you use table AddressData to transfer data, the address data for the one-time vendor is read from the purchase order into the invoice and is then either overwritten or supplemented by the fields of table AddressData.

The purchase order for the one-time vendor has the following stored data: Name 'SAP AG', postal code '60000' and street and building number 'Neurottstraße 16'. You receive an invoice with the one-time vendor address: Name 'SAP AG', postal code '69190', and place 'Walldorf'. Enter the following data:

AddressData table

ACC_1_TIME (Indicator one-time vendor): X

NAME (Name): SAP AG

POSTL_CODE (Postal code): 69190

CITY (Place): Walldorf

The invoice is posted with the following one-time vendor: Name 'SAP AG' street and building number 'Neurottstraße 16', postal code '69190', city 'Walldorf'.

For more information, see the parameter documentation for the table AddressData.

Example: Incoming invoice for different payee
This example shows you which address data you must enter in the table AddressData to enter and post an invoice for a different payee.

You receive an invoice for the different payee with name 'SAP AG', postal code '69190', place 'Walldorf', bank number '38070724' and account number '4711'.

Enter the following data:

AddressData table

ACC_1_TIME (Indicator one-time vendor): ' '

NAME (Name): SAP AG

POSTL_CODE (Postal code): 69190

CITY (Place): Walldorf

BANK_NO (Bank number): 38070724

BANK_ACCT (Bank account number): 4711

For more information, see the parameter documentation for the table AddressData.

Parameters
HEADERDATA
ADDRESSDATA
INVOICEDOCNUMBER
FISCALYEAR
ITEMDATA
ACCOUNTINGDATA
GLACCOUNTDATA
MATERIALDATA
TAXDATA
WITHTAXDATA
VENDORITEMSPLITDATA
RETURN
EXTENSIONIN

Exceptions
Function Group
MRM_BAPI

Note 1082841 - MMPV date check for Material Ledger

2010-03-12T06:42:00.001-08:00

Symptom

You need to run MMPV (period roller). You want to prevent shifting to a future period by mistake (for example, a common mistake is running MMPV twice at the beginning of a month).

Other terms

MMPV, MARV, period roller, period shift, material ledger, MMPV_READ_NOTE, MMPV_DATE_CHECK

Reason and Prerequisites

In the event that MMPV is mistakenly executed twice at the beginning of a period, the active period could be shifted to a future period. As a consequence, all subsequent goods movement would be posted to the wrong period. To correct such errors is difficult, especially when Material Ledger is active.

Solution

This note provides a feature to prevent using MMPV to shift into a future period. This feature is activated automatically after implementing this note and works with our without Material Ledger active. MMPV can continue only if the new period is within 10 days (by default but is configurable) away from the current date in the system. Otherwise, it will terminate and no change will be made.
To disable this feature, you must set parameter ID MMPV_READ_NOTE with the current date in the user parameters in form YYYYMMDD (Y = year, M = month, D = day).
To change the number of days to a value other than the default (10 days), set the following entry in table CKMLMVADMIN:

KKEY : MMPV_NUMBER_DAYS_ALLOWED

KDATA : <number of days MMPV is allowed>

Only integers are allowed, with 0 meaning MMPV is allowed only on or after the first day of a new period. If the value is greater than the actual number of days in a period then it means MMPV is allowed for the entire month. Any invalid entry in the KDATA field will be ignored and the default value will be used.
Carry out the following manual stpes, then implement the attached note.

2. Use transaction SE37 to create function module MMPV_DATE_CHECK with the following attributes:

Function group : MLCCS_MATERIAL_MASTER
Short text : Date check for period roller

Import parameters:

Parameter Name
Type
Associated Type

I_NEW_LFGJA
TYPE
BDATJ

I_NEW_LFMON
TYPE
MONAT

I_BUKRS
LIKE
T001-BUKRS

I_FY_VARIANT
TYPE
PERIV

Exceptions:

MMPV_BLOCKED

ERROR_OCCURRED

Sym : 099

Text : Transaction MMPV cannot be executed. Please refer to SAP note 1082841

Save and activate the changes.

AUSNA : 99

ABBRU : X

SORT : 99

KTEXT : MMPV_DATE_CHECK: Error occurred (Note 1082841).

AUSNA : 99
KTEXT : MMPV_DATE_CHECK: Error occurred (Note 1082841).

6. Implement the attached program corrections.

IDOC USER EXIT UNPLANNED DELIVERY CHARGES

2010-03-10T15:33:00.001-08:00

"EXIT_SAPLMRMH_015"

MRM_INVOICE_CREATE and posting on GL
Posted: May 26, 2008 10:34 AM in response to: Marian Morzol

Hi
It is possible to post to the G/L accounts using IDoc.
Please check the following
- Check whether the Posting to G/L accounts is activated for MIRO
SPRO-> Logistics Invoice Verification-> Incoming Invoice-> Activate Direct Posting to G/L Accounts and Material Accounts
- Check if the customizing had been done for posting to G/L accounts in OBCE & OBCB (if required)
In your code please check if you have added e_Change = X
Thsi is the sample code
DATA: s_frseg TYPE mmcr_frseg,
s_co TYPE cobl_mrm.
READ TABLE t_frseg INDEX 1 INTO s_frseg.
s_frseg-wrbtr = s_frseg-wrbtr - 1.
MODIFY t_frseg INDEX 1 FROM s_frseg.
s_co-bukrs = e_rbkpv-bukrs.
s_co-mwskz = s_frseg-mwskz.
s_co-wrbtr = 1.
s_co-saknr = '0000400000'.
s_co-kostl = '1000'.
s_co-shkzg = 'S'.
APPEND s_co TO t_co.
e_change = 'X'.
Please go through the SAP note 427137 , if you are working in rlease 4.6C
Thanks & Regards
Kishore
Edited by: Kishore Kumar Chiluka on May 26, 2008 10:40 AM

Invoice Posting: User Exits

2010-03-10T09:41:00.001-08:00

MM08R002 Tolerance checks
other than user exits ( customer exists used in invoice)
MM08R001 ERS (conventional Invoice Verification)
MM08R002 Tolerance checks
LMR1M001 Transfer of document header and item data,
account assignment proposal for invoices for blanket POs
LMR1M002 Account grouping for GR/IR account determination
LMR1M003 Number assignment in Logistics Invoice Verification
LMR1M004 Item text in follow-on documents
LMR1M005 Change criteria for releasing parked documents for posting
LMR1M006 Change XML data for BAPI call CreateFromData
RMVKON00 Consignment/pipeline settlement
MRMH0001 ERS (Logistics Invoice Verification)
MRMH0002 EDI invoice receipt (Logistics Invoice Verification)
MRMH0003 Revaluation (Logistics Invoice Verification)
MRMN0001 Message output for Invoice Verification*
Hope it's useful for you
G.Ganesh Kumar

SAP EDI IDOC Blog

2010-03-02T08:01:00.001-08:00

http://sap-idoc2edi-consulting.com/

SAP IDoc Blog

2010-03-02T07:52:00.001-08:00

http://it.toolbox.com/blogs/ehadzipetros

SAP Note: 800866 Invoice IDoc with Unplanned Delivery Cost

2010-03-01T10:00:00.001-08:00

In MM, an invoice cannot be posted if delivery costs were specified whenthe invoice was created in SUS. The IDoc terminates with status 51 'application document not posted' and the system issues error message M8 534 'Balance not zero'. The balance corresponds to the delivery costs.

Reason and Prerequisites

The delivery costs are not read in MM in standard inbound processing.

Solution

If you want to sendi nvoiceswith delivery costs from SUS to MM, you must use Transaction CMOD to program the EXIT_SAPLMRMH_014 user exit as follows:

Create a customer project and use Transaction CMOD to call it. Add the MRMH0002 enhancement and the EXIT_SAPLMRMH_014 component. Insert the source code into the ZXM08U25 include.

DATA: ls_data_s01 type E1EDS01,
lv_beznk type MRM_RBKPV-beznk.

IF I_IDOC_DATA-SEGNAM = 'E1EDS01'.
ls_data_s01 = I_IDOC_DATA-SDATA.

IF ls_data_s01-sumid = '020'.

lv_beznk = ls_data_s01-summe.

E_RBKPV-BEZNK = lv_beznk.

E_CHANGE = 'X'.

ENDIF.

INVOICE UNPLANNED DELIVERY COST IDOC

2010-03-01T09:58:00.001-08:00

To post unplanned delivery cost using INVOIC01 we referenced OSS Note
800866. We continued to have issues with determining the tax jurisdiction
code and received this response:
I have done a detailed analysis and the
solution I propose is to use the FM 'EXIT_SAPLMRMH_014'. The options
are:
1. If the field TXJCD is blank in the idoc and if the tax code for the
unplanned delivery cost is same in invoice item and in the refered
PO item, then you can fill E_RBKPV-TXJCD_BNK from the PO item in the FM
'EXIT_SAPLMRMH_014'.
2. If the tax code for the unplanned delivery cost is not same as the
tax code in invoice item or in the refered PO item, you can find the
TXJCD from the tax condition's data for the tax code and copy it to
E_RBKPV-TXJCD_BNK within the user exit.
3. If the field TXJCD is filled in the idoc, you can fill the
E_RBKPV-TXJCD_BNK in the user exit from here.
We choice option 3 and we are successfully posting unplanned delivery cost
using INVOIC01.

GRN INVOICE WORKFLOW

2010-03-01T09:52:00.001-08:00

We have a workflow which is triggered when an invoice is parked. It sends a work item to the contact center project manager to create a GRN.

Our problem is that when the GR is created through the transaction and not through the work item, the work item remains in the user's inbox. Is there a way to change the status of the work item to 'complete' and remove it from the user's inbox?

What I would do in this case is put in a parallel step with the work item that listens for the creation of the GR. When this event is received, the parallel step will terminate the work item in the user's inbox.

There is another approach which is to use terminating events on the work item but this requires you to specify the GR creation method as asynchronous.

Can I park incoming invoices when no goods entry is posted?

2010-03-01T09:46:00.001-08:00

EXPERT RESPONSE FROM: Axel Angeli

QUESTION POSED ON: 13 May 2003
I am working with INVOIC01 in 4.6C using INVL as the process code. The problem I am having is that I want to post or park an invoice when goods receipt has not been posted. It seems that SAP rejects such invoices by default. Unfortunately, the majority of invoices have no goods receipt when received through EDI.
Also, is there a way to automatically clear these invoices when goods receipts arrive?

This is an application issue of your MM-PUR customizing.
The IDoc is handed over by the IDoc engine to application processing. It is the application that rejects the invoice. You have to see this issue with your MM-PUR functional team so that they set up customizing or prepare a user-exit that allows to accept invoices in this cases. Automatic clearance of blocked invoices has not been possible in older releases. I have not checked if it possible in 4.6. What you can do, is set up a custom workflow that does the job triggered by the goods receipt.

MESSAGE TYPE FOR SELF BILLING OR ERS

2010-03-01T09:36:00.001-08:00

I have a question about SBWAP message type and EDI. I am looking to send ERS output (self-billing invoice), which generates IDocs with Message Type SBWAP, to suppliers using EDI X12. Which EDI message type (ANSI X12) can I use to send this? Do you know of any company that sends SBWAP to suppliers?

Self billing is usually done via FM IDOC_OUTPUT_GSVERF and IDoc type GSVERF01 . The matching ANSI X.12 transaction is 810 (invoice/credit). Any of the automotive manufacturers (Daimler, Ford, Volkswagen BMW, Peugeout, Renault, etc.) use self billing intensively, and so do many of the bigger automotive suppliers in the context of central billing.

SAP Searches Using Google Advanced Search

2010-03-01T09:35:00.001-08:00

==========================================================================================================

Vendor invoices and adapting to unexpected charges or discounts

2010-03-01T09:18:00.001-08:00

Suppose a vendor's invoice includes an unanticipated surcharge, discount or freight charge at the HEADER level (=not at the PO-line-item level). Such an amount was not part of the original PO, so we'd be booking a non-PO-based additional amount. How can we book the unanticipated charge using the INVOIC02 IDOC?

One approach might be to create an additional E1EDP01 segment, (or the appropriate sub-segments, like E1EDP26, etc.), but then SAP would want to know the GL account (and cost center?) to which book that amount. I cannot determine which INVOIC segment would carry such account-assignment information.

The offset to that additional E1EDP01 segment would be to adjust the net amount of the invoice within the E1EDS01 segment (SUMID = 010 for net amount, SUMME for the new net amount, WAERQ for the currency-code).

Can you provide some assistance?
===============================

The question you raise needs to be properly discussed with your auditors. Generally it can be said that an incoming billing IDoc is a legal document, like a paper invoice is also a legal document. This means that you are not allowed to change the information contained therein when booking them into your system. So if unexpected surcharges occur, you have to book them as it is sent by the vendor.

How to book the additional amounts? Mapping them into an additional E1EDP01 may be the proper approach. Finding the correct GL account is not the task of the IDoc mapping software, however, but needs to be carried out automatically (or with some assistance of the billing manager) within R/3. Usually this works the same way as it does when you would create a new item in your purchase order. I have limited information about how your SAP installation is set up, but a common approach would be create an appropriate item category and customize the finding of the proper COPA and FI accounting from the item category.

But principally, your approach is designed well, and should work that way

Unplanned Delivery Cost – Idoc - Invoic02

2010-03-01T08:44:00.001-08:00

Use the user exit EXIT_SAPLMRMH_014.

OSS note 119092 identifies the solution to not being able to process planned freight as processing it as unplanned freight.

You can account unplanned delivery costs with the aid of User Exit EXIT_SAPLIEDI_111 (for Transaction MR01) or EXIT_SAPLMRMH_014 (for Transaction MR1M / MIRO.

FU EXIT_SAPLMRMH_014
____________________________________________________
Short Text
Customer Exit: EDI Invoice Receipt - Change IDoc Segment

Functionality
This customer-specific function module is called after the system has read each IDoc segment while processing IDocs. This allows you to use the information in each IDoc segment to determine data in the invoice document to be created in a different way to that in the standard system. In addition to the IDoc segment, the document header data and the document items created so far are available.

Notes
The system only adopts the change if parameter E_CHANGE = 'X' is passed on.

Parameters
I_IDOC_DATA
E_CHANGE
E_RBKPV
T_FRSEG

Exceptions
ERROR_MESSAGE

Function Group
XM08

SAP R/3 форум ABAP консультантов View topic - IDoc User Exit List

2010-03-01T07:12:00.001-08:00

IDoc Inbound User Exits
1. ACC_BILLING
Accounting: Post invoice (OAG: LOAD RECEIVABLE)
- ACBAPI01 EXIT_SAPLACC4_001 Accounting: Customer enhancement to BAPI interfaces
2. ACC_EMPLOYEE_EXP
FI/CO: HR posting GL (AcctngEmplyeeExenses)
- ACBAPI01 EXIT_SAPLACC4_001 Accounting: Customer enhancement to BAPI interfaces
3. ACC_EMPLOYEE_PAY
FI/CO: HR posting AP (AcctngEmplyeePaybles)
- ACBAPI01 EXIT_SAPLACC4_001 Accounting: Customer enhancement to BAPI interfaces
4. ACC_EMPLOYEE_REC
FI/CO: HR posting AR (AcctngEmplyeeRcvbles)
- ACBAPI01 EXIT_SAPLACC4_001 Accounting: Customer enhancement to BAPI interfaces
5. ACC_GL_POSTING
Accounting: General G/L account posting
- ACBAPI01 EXIT_SAPLACC4_001 Accounting: Customer enhancement to BAPI interfaces
6. ACC_GOODS_MOVEMENT
Accounting: Post goods movement (OAG: POST JOURNAL)
- ACBAPI01 EXIT_SAPLACC4_001 Accounting: Customer enhancement to BAPI interfaces
7. ACC_INVOICE_RECEIPT
Accounting: Post invoice receipt (OAG: LOAD PAYABLE)
- ACBAPI01 EXIT_SAPLACC4_001 Accounting: Customer enhancement to BAPI interfaces
8. ACLPAY Accounting: Inbound invoice
- ACCID001 EXIT_SAPLACC1_031 IDoc ACLPAY: Userexit for creditor in accounting document
- ACCID001 EXIT_SAPLACC1_032 IDoc ACLPAY: Userexit for GL posting in accounting document
- ACCID001 EXIT_SAPLACC1_033 IDoc ACLPAY: Userexit for taxes in accounting document
9. ACLREC
Accounting: Billing document
- ACCID001 EXIT_SAPLACC1_011 IDoc ACLREC: Userexit for debitor in accounting document
- ACCID001 EXIT_SAPLACC1_012 IDoc ACLREC: Userexit for GL posting in accounting document
- ACCID001 EXIT_SAPLACC1_013 IDoc ACLREC: Userexit for taxes
10. ACPJMM
Posting in accounting from materials management
- ACCID001 EXIT_SAPLACC1_021 IDoc ACPJOU: Userexit for GL posting in accounting document
11. ARTMAS
Create and change of material master (Retail)
- MGV00003 EXIT_SAPL1001_003 Enhancement for article master: IDoc inbound
12. BLAOCH
Purchasing contract change
- MM06E002 EXIT_SAPLEINN_001 Customer enhancements for Idocs: contracts
- MM06E002 EXIT_SAPLEINN_002 Customer enhancements for Idocs: contracts
- MM06E002 EXIT_SAPLEINN_003 Customer enhancements for Idocs: contracts
13. BLAORD
Purchasing contracts
- MM06E002 EXIT_SAPLEINN_001 Customer enhancements for Idocs: contracts
- MM06E002 EXIT_SAPLEINN_002 Customer enhancements for Idocs: contracts
- MM06E002 EXIT_SAPLEINN_003 Customer enhancements for Idocs: contracts
14. BLAREL
Release order documentation for distributed contracts
- MM06E001 EXIT_SAPLEINM_004 Customer enhancements for release documentation inbound
15. COND_A
Conditions: master data for price determination
- VKOI0001 EXIT_SAPLVKOI_001 Interchange of Conditions: Inbound Processing Modifications E1KOMG Segment
- VKOI0001 EXIT_SAPLVKOI_002 Interchange of Conditions: Inbound Processing Customer Segments
16. CREMAS
Distribute vendor master
- VSV00001 EXIT_SAPLKD02_001 Inbound: Read and process vendor segments
17. DEBMAS
Customer master
- VSV00001 EXIT_SAPLVV02_001 Inbound: Read and update additional customer master segments
18. DELINS
Delivery schedule/JIT schedule
- VED40001 EXIT_SAPLVED4_001 Modify Warnings in Table XVBFS
- VED40001 EXIT_SAPLVED4_002 Copying Data to Screens for Incoming EDI Docs
- VED40001 EXIT_SAPLVED4_003 Customer-Specific Changes in the Workflow Parameters
- VED40001 EXIT_SAPLVED4_004 Determination of mail receiver during inbound processing
19. DESADV
Delivery: Shipping notification
- LMELA010 EXIT_SAPLEINM_010 Customer enhancement shipping notification inbound: line item
- MM06E001 EXIT_SAPLEINM_006 Customer enhancements for shipping notification inbound
- V55K0001 EXIT_SAPLV55K_001 Delivery (inbound): Take data
- V55K0002 EXIT_SAPLV55K_002 Delivery (inbound): Prepare processing
- V55K0003 EXIT_SAPLV55K_003 Delivery (inbound): Evaluate result
- V55K0011 EXIT_SAPLV55K_011 Shipping notification (inbound): Take data
- V55K0012 EXIT_SAPLV55K_012 Shipping notification (inbound): Prepare processing
- V55K0013 EXIT_SAPLV55K_013 Shipping notification (inbound): Evaluate result
20. DOCMAS
Master document
- CVDS0001 EXIT_SAPLCVALE_001 Userexit for ALEDVS (DOCMAS inbound)
21. DOLMAS
Document-object links
- CVDS0001 EXIT_SAPLCVALE_003 Userexit for ALEDVS (DOLMAS inbound)
22. EDLNOT
EDL delivery notes
- VED40001 EXIT_SAPLVED4_001 Modify Warnings in Table XVBFS
- VED40001 EXIT_SAPLVED4_002 Copying Data to screens for Incoming EDI Docs
- VED40001 EXIT_SAPLVED4_003 Customer-Specific Changes in the Workflow Parameters
- VED40001 EXIT_SAPLVED4_004 Determination of mail receiver during inbound processing
23. FIDCC1
Send entire FI documents (user exit 003/4)
- F050S001 EXIT_SAPLF050_002 IDoc inbound: read user-defined IDoc segment
- F050S002 EXIT_SAPLF050_004 FIDCC1 IDoc inbound: Change IDoc / do not process
- F050S005 EXIT_SAPLF050_008 IDoc inbound: change fields in ACC structures (FI document)
- F050S005 EXIT_SAPLF050_009 IDoc inbound: change fields in parked documents
24. FIDCC2
Send entire FI documents (user exit 005/6)
- F050S001 EXIT_SAPLF050_002 IDoc inbound: read user-defined IDoc segment
- F050S003 EXIT_SAPLF050_006 FIDCC2 IDoc inbound: Change IDoc / do not process
- F050S005 EXIT_SAPLF050_008 IDoc inbound: change fields in ACC structures (FI document)
- F050S005 EXIT_SAPLF050_009 IDoc inbound: change fields in parked documents
25. FIDCMT
Sending single items for FI-GL
- F050S001 EXIT_SAPLF050_002 IDoc inbound: read user-defined IDoc segment
- F050S005 EXIT_SAPLF050_008 IDoc inbound: change fields in ACC structures (FI document)
26. FINSTA
Bank Statement
- FEDI0005 EXIT_SAPLIEDP_201 FI-EDI: inbound - bank statement/ Lockbox - Final processing
- FEDI0005 EXIT_SAPLIEDP_202 FI-EDI: inbound - bank statement/ Lockbox - Processing of segments
27. FIROLL
General ledger rollup for FI-GL (delta f. line items FIDCMT)
- F050S001 EXIT_SAPLF050_002 IDoc inbound: read user-defined IDoc segment
28. GSVERF
Cred. memo procedure
- VED50001 EXIT_SAPLVED5_001 User Exit for Condition Value Tolerances in the Self- Billing Procedure
- VED50001 EXIT_SAPLVED5_005 Customer-Specific Changes in Workflow Parameters
- VED50001 EXIT_SAPLVED5_006 Copying Data to Screens for Incoming EDI Docs
29. HRMD_A
HR: Master data and organizational data (appl. system)
- RHALE001 EXIT_SAPLRHA0_002 HR-CA: ALE inbound processing: Export parameter
- RHALE001 EXIT_SAPLRHAL_002 HR-CA: ALE inbound processing: Change info type data
- RHALE001 EXIT_SAPLRHAL_004 HR-CA: ALE inbound processing: conversion segment/ info type
30. INFREC
Purchasing info record
- MMAL0004 EXIT_SAPLMEAI_004 ALE source list distribution: inbound processing userdefined data
- MMAL0004 EXIT_SAPLMEAI_003 ALE purchasing info record distribution: inbound processing segments
31. INVOIC
Invoice / Billing document
- FEDI0001 EXIT_SAPLIEDI_001 FI-EDI: Invoice receipt - Determine G/L account per invoice line
- FEDI0001 EXIT_SAPLIEDI_002 FI-EDI: Invoice receipt - Determine add. acct assignm. per line item
- FEDI0001 EXIT_SAPLIEDI_003 FI-EDI: Invoice receipt - Fill the screen field 'Allocation'
- FEDI0001 EXIT_SAPLIEDI_004 FI-EDI: Invoice receipt - Determine the segment text
- FEDI0001 EXIT_SAPLIEDI_005 FI-EDI: Invoice receipt - Determine the name of the BDC session
- FEDI0001 EXIT_SAPLIEDI_011 MM-EDI: Invoice receipt - Determine purchase order item
- FEDI0001 EXIT_SAPLIEDI_101 FI-EDI: Invoice receipt INVOIC01 - additional assignment
- FEDI0001 EXIT_SAPLIEDI_102 FI-EDI: Invoice receipt INVOIC01 - add data
- FEDI0001 EXIT_SAPLIEDI_111 MM-EDI: Invoice receipt INVOIC01 - additional assignment
- FEDI0001 EXIT_SAPLIEDI_112 MM-EDI: Invoice receipt INVOIC01 - add data
- MRMH0002 EXIT_SAPLMRMH_011 Logistics Invoice Verification:inboud EDI message, company code
- MRMH0002 EXIT_SAPLMRMH_012 Logistics Invoice Verification:inboud EDI message, control flags
- MRMH0002 EXIT_SAPLMRMH_013 Logistics Invoice Verification:inboud EDI message, assignment
- MRMH0002 EXIT_SAPLMRMH_014 Logistics Invoice Verification:inboud EDI message, segments
- MRMH0002 EXIT_SAPLMRMH_015 Logistics Invoice Verification:inbound EDI message, before posting
32. LIKOND
Listing conditions
- WSOR0001 EXIT_SAPLWSOI_001 Enhancement for assortments: inbound IDoc
33. MATMAS
Material Master
- MGV00001 EXIT_SAPLMV02_002 Enhancement for material master IDoc: Update
34. MRESCR
Create reservation
- SAPLMEWB EXIT_SAPLMEWB_001 Customer exit for processing of reservations via BAPIs
35. ORDCHG
Purchase order/order change
- MM06E001 EXIT_SAPLEINM_012 MM EDI ORDERS/ ORDCHG: enhancement configuration
- MM06E001 EXIT_SAPLEINM_013 MM EDI ORDERS/ ORDCHG: enhancement configuration
- VEDB0001 EXIT_SAPLVEDB_001 SD EDI incoming change orders: read additional data from IDoc
- VEDB0001 EXIT_SAPLVEDB_002 SD EDI incoming change orders: additional data for dynpros
- VEDB0001 EXIT_SAPLVEDB_003 SD EDI incoming change orders: further activities after calling
- VEDB0001 EXIT_SAPLVEDB_004 SD EDI incoming change orders: closing activities per
- VEDB0001 EXIT_SAPLVEDB_005 SD EDI incoming change orders: closing activities by order block
- VEDB0001 EXIT_SAPLVEDB_006 SD EDI incoming change orders: setting order type
- VEDB0001 EXIT_SAPLVEDB_007 SD EDI incoming change orders: additional checks of IDoc
- VEDB0001 EXIT_SAPLVEDB_008 SD EDI incoming change orders: error handling
- VEDB0001 EXIT_SAPLVEDB_009 SD EDI incoming change orders: additional checks of IDoc segments
- VEDB0001 EXIT_SAPLVEDB_010 SD EDI incoming change orders: manipulation of status ecords
- VEDB0001 EXIT_SAPLVEDB_012 SD EDI incoming change orders: change internal table
36. ORDERS
Purchase order / order
- MCP20008 EXIT_SAPLMCP2_008 User exit: Processing of purchase order header
- MCP20008 EXIT_SAPLMCP2_009 User exit: Processing of purchase order item
37. ORDERS
Purchase order / order
- MM06E001 EXIT_SAPLEINM_012 MM EDI ORDERS/ ORDCHG: enhancement configuration
- MM06E001 EXIT_SAPLEINM_013 MM EDI ORDERS/ ORDCHG: enhancement configuration
- VEDA0001 EXIT_SAPLVEDA_001 SD EDI incoming orders: read additional data from IDoc
- VEDA0001 EXIT_SAPLVEDA_002 SD EDI incoming orders: additional data for dynpros
- VEDA0001 EXIT_SAPLVEDA_003 SD EDI incoming orders: further activities after calling
- VEDA0001 EXIT_SAPLVEDA_004 SD EDI incoming orders: closing activities per order
- VEDA0001 EXIT_SAPLVEDA_005 SD EDI incoming orders: closing activities by order block
- VEDA0001 EXIT_SAPLVEDA_006 SD EDI incoming orders: setting order type
- VEDA0001 EXIT_SAPLVEDA_007 SD EDI incoming orders: number of ordering party
- VEDA0001 EXIT_SAPLVEDA_008 SD EDI incoming orders: error handling
- VEDA0001 EXIT_SAPLVEDA_009 SD EDI incoming orders: additional checks of IDoc segments
- VEDA0001 EXIT_SAPLVEDA_010 SD EDI incoming orders: manipulation of status records
- VEDA0001 EXIT_SAPLVEDA_011 SD EDI incoming orders: change internal table
- WVFB0001 EXIT_SAPLWVFB_002 Customer exists for store order PO confirmationdata seg.
38. ORDRSP
Purchase order / order confirmation
- MM06E001 EXIT_SAPLEINM_005 Customer enhancements for order confirmation inbound
- MM06E001 EXIT_SAPLEINM_007 Customer enhancements inbound confirmation: reading
- MM06E001 EXIT_SAPLEINM_008 Customer enhancements inbound confirmation: final
- WVMI0001 EXIT_SAPLWVMI_003 ORDRSP VMI inbound, modification before creating purchase order
39. PORDCR
Create purchase order
- SAPLMEWP EXIT_SAPLMEWP_002 Customer exit for processing of purchase orders via BAPIs
40. PREQCR
Create purchase requisition
- SAPLMEWQ EXIT_SAPLMEWQ_001 Customer exit for processing of requisitions via BAPIs
41. PROACT
Stock and sales data
- WVMI0001 EXIT_SAPLWVMI_002 IDoc PROACT inbound: prior to processing
42. REMADV
Payment advice
- FEDI0002 EXIT_SAPLIEDP_101 FI-EDI: Incoming pmnt advice - Extended allocatn of IDOC -> applicatn data
- FEDI0002 EXIT_SAPLIEDP_102 FI-EDI: Incoming pmnt adivce - Closing allocatn of IDOC -> applicatn data
43. REQOTE
Inquiry
- VEDQ0001 EXIT_SAPLVEDQ_001 SD EDI inbound inquiry: read additional data from IDoc
- VEDQ0001 EXIT_SAPLVEDQ_002 SD EDI inbound inquiry: additional data for dynpros
- VEDQ0001 EXIT_SAPLVEDQ_003 SD EDI inbound inquiry: further activities after calling
- VEDQ0001 EXIT_SAPLVEDQ_004 SD EDI inbound inquiry: closing activities per inquiry
- VEDQ0001 EXIT_SAPLVEDQ_005 SD EDI inbound inquiry: closing activities by inquiry block
- VEDQ0001 EXIT_SAPLVEDQ_006 SD EDI inbound inquiry: setting inquiry type
- VEDQ0001 EXIT_SAPLVEDQ_007 SD EDI inbound inquiry: number of sold-to party
- VEDQ0001 EXIT_SAPLVEDQ_008 SD EDI inbound inquiry: error handling
- VEDQ0001 EXIT_SAPLVEDQ_009 SD EDI inbound inquiry: additional checks of IDoc segments
- VEDQ0001 EXIT_SAPLVEDQ_010 SD EDI inbound inquiry: manipulation of status records
- VEDQ0001 EXIT_SAPLVEDQ_011 SD EDI inbound inquiry: change internal table
44. SBINV
Credit memo procedure with invoice creation
- VED50001 EXIT_SAPLVED5_002 User Exit for messages in the Self-Billing Procedure SBINV
- VED50001 EXIT_SAPLVED5_003 User Exit for Tolerances in the Self- Billing Procedure SBINV
- VED50001 EXIT_SAPLVED5_004 Customer-Function for changing invoice data SBINV
- VED50001 EXIT_SAPLVED5_005 Customer-Specific Changes in Workflow Parameters
- VED50001 EXIT_SAPLVED5_006 Copying Data to Screens for Incoming EDI Docs
45. SDPACK
Packing confirmation
- VMDE0001 EXIT_SAPLVMDE_001 Shipping Interface: Error Handling - Inbound IDoc
- VMDE0004 EXIT_SAPLVMDE_004 Shipping Interface: Message SDPACK (Packing, Inbound)
46. SDPICK
Picking confirmation
- VMDE0001 EXIT_SAPLVMDE_001 Shipping Interface: Error Handling - Inbound IDoc
- VMDE0003 EXIT_SAPLVMDE_003 Shipping Interface: Message SDPICK (Picking, Receipt)
47. SHP_IBDLV_CONFIRM_DECENTRAL
Confirmation (Inbound Delivery)
- V50B0001 EXIT_SAPLV50I_002 User exit for BAPI Verification of Inbound Deliveries
48. SHP_IBDLV_SAVE_REPLICA
BAPI Function Module for Duplication of Outbound Deliveries
- V50B0001 EXIT_SAPLV50I_001 User exit for BAPI Duplication of Inbound Deliveries
49. SHP_OBDLV_CONFIRM_DECENTRAL
Confirmation (Customer Delivery)
- V50B0001 EXIT_SAPLV50I_004 User exit for BAPI Verification of Outbound Deliveries
50. SHP_OBDLV_SAVE_REPLICA
BAPI Function Module for Duplication of Outbound Deliveries
- V50B0001 EXIT_SAPLV50I_003 User exit for BAPI Duplication of Outbound Deliveries
51. SHPCON
Delivery: Shipping confirmation
- V55K0001 EXIT_SAPLV55K_001 Delivery (inbound): Take data
- V55K0002 EXIT_SAPLV55K_002 Delivery (inbound): Prepare processing
- V55K0003 EXIT_SAPLV55K_003 Delivery (inbound): Evaluate result
- V55K0011 EXIT_SAPLV55K_011 Shipping notification (inbound): Take data
- V55K0012 EXIT_SAPLV55K_012 Shipping notification (inbound): Prepare processing
- V55K0013 EXIT_SAPLV55K_013 Shipping notification (inbound): Evaluate result
52. SHPMNT
Shipping outbound
- V55K0020 EXIT_SAPLV55K_020 IDoc SHPMNT: Modification Control/ Data before processing
- V55K0021 EXIT_SAPLV55K_021 Processing of segments IDoc SHPMNT
- V55K0022 EXIT_SAPLV55K_022 Update of user defined tables for inbound IDoc SHPMNT
53. SRCLST
Source List
- MMAL0002 EXIT_SAPLMEAI_001 ALE source list distribution: inbound processing segments
- MMAL0002 EXIT_SAPLMEAI_002 ALE source list distribution: inbound processing user defined data
54. SRVMAS
Master data service master
- BASI0001 EXIT_SAPLBASI_001 Userexit IDoc inbound service master: segment
- BASI0001 EXIT_SAPLBASI_002 Userexit IDoc inbound service master: database
55. TPSSHT
Shipping planning system: Transfer planned shipments
- V56I0010 EXIT_SAPLV56I_010 IDoc TPSSHT01: Input of planned shipments: Modification of IDoc segments
- V56I0010 EXIT_SAPLV56I_011 IDoc TPSSHT01: Input of planned shipments: modification of transport tab, processing
- V56I0010 EXIT_SAPLV56I_012 IDoc TPSSHT01: Input of planned shipments: update of own tables
56. WHSCON
Delivery: Stock confirmation
- V55K0001 EXIT_SAPLV55K_001 Delivery (inbound): Take data
- V55K0002 EXIT_SAPLV55K_002 Delivery (inbound): Prepare processing
- V55K0003 EXIT_SAPLV55K_003 Delivery (inbound): Evaluate result
- V55K0011 EXIT_SAPLV55K_011 Shipping notification (inbound): Take data
- V55K0012 EXIT_SAPLV55K_012 Shipping notification (inbound): Prepare processing
- V55K0013 EXIT_SAPLV55K_013 Shipping notification (inbound): Evaluate result
57. WMBBIN
Block Storage Bins
- MWMIDI01 EXIT_SAPLLIDI_001 Customer enhancement for error handling of inbound IDoc
- MWMIDI04 EXIT_SAPLLIDI_004 Customer enhancement for IDoc WMBBID01
58. WMCATO
Reversal/Reversal request for transfer order
- MWMIDI01 EXIT_SAPLLIDI_001 Customer enhancement for error handling of inbound IDoc
- MWMIDI03 EXIT_SAPLLIDI_003 Customer enhancement for IDoc WMCAI01
59. WMINVE
Inventory count input
- MWMIDO07 EXIT_SAPLLMDE_001 Customer enhancement for error handling of inbound IDoc
- MWMIDO09 EXIT_SAPLLMDE_003 Customer enhancement for message WMINVE
- MWMIDO07 EXIT_SAPLLMDE_001 Customer enhancement for error handling of inbound IDoc
60. WMMBXY
IDoc Report goods movements in IM
- MWMIDO08 EXIT_SAPLLMDE_002 Customer enhancement for message WMMBXY (goods movement) inbound
61. WMSUMO
Move storage unit
- MWMIDI01 EXIT_SAPLLIDI_001 Customer enhancement for error handling of inbound IDoc
- MWMIDI06 EXIT_SAPLLIDI_006 Customer enhancement for IDoc WMSUID01
62. WMTOCO
Transfer order
- MWMIDI01 EXIT_SAPLLIDI_001 Customer enhancement for error handling of inbound IDoc
- MWMIDI02 EXIT_SAPLLIDI_002 Customer enhancement for IDoc WMTCID01
63. WMTORD
Transfer order
- MWMIDO07 EXIT_SAPLLMDE_001 Customer enhancement for error handling of inbound IDoc
- MWMIDO10 EXIT_SAPLLMDE_004 Customer enhancement for message WMTORD (Create TO) inbound
- MWMIDO11 EXIT_SAPLLMDE_005 Customer enhancement for message WMTORD (Create TO) inbound
64. WMTREQ
Create/Cancel transfer order
- MWMIDI01 EXIT_SAPLLIDI_001 Customer enhancement for error handling of inbound IDoc
- MWMIDI05 EXIT_SAPLLIDI_005 Customer enhancement for IDoc WMTRID01
65. WPUBON
POS interface: Upload sales documents (compressed)
- WPUE0002 EXIT_SAPLWPUE_104 IDoc WPUBON01: prior to inbound processing
- WPUE0002 EXIT_SAPLWPUE_105 Check, whether transaction of IDoc WPUBON01 is compressable
- WPUE0002 EXIT_SAPLWPUE_106 IDoc WPUBON01: processing user segment
- WPUE0002 EXIT_SAPLWPUE_109 IDoc WPUBON01: after to inbound processing
66. WPUFIB
POS interface: Upload Fin.Acc. interface SRS/POS
- WPUE0002 EXIT_SAPLWPUE_130 IDoc WPUFIB01: prior to update
- WPUE0002 EXIT_SAPLWPUE_131 IDoc WPUFIB01: processing user
67. WPUFIB
POS interface: Upload Fin.Acc. interface SRS/POS
- WPUE0002 EXIT_SAPLWPUE_132 IDoc WPUFIB01: prior to inbound processing
- WPUE0002 EXIT_SAPLWPUE_139 IDoc WPUFIB01: after to inbound processing
68. WPUKSR
POS upload cashier data
- WPUE0002 EXIT_SAPLWPUE_120 IDoc WPUKSR01: prior to update
- WPUE0002 EXIT_SAPLWPUE_122 IDoc WPUKSR01: processing user segment
- WPUE0002 EXIT_SAPLWPUE_123 IDoc WPUKSR01: prior to inbound processing
- WPUE0002 EXIT_SAPLWPUE_129 IDoc WPUKSR01: after to inbound processing
- WPUE0002 EXIT_SAPLWPUE_152 IDoc WPUTAB01: prior to inbound processing
- WPUE0002 EXIT_SAPLWPUE_159 IDoc WPUTAB01: after to inbound processing
69. WPUUMS
POS interface: Upload sales data (compressed)
- WPUE0002 EXIT_SAPLWPUE_110 IDoc WPUUMS01: prior to update
- WPUE0002 EXIT_SAPLWPUE_112 IDoc WPUUMS01: prior to inbound processing
- WPUE0002 EXIT_SAPLWPUE_113 IDoc WPUUMS01: processing user segment
- WPUE0002 EXIT_SAPLWPUE_119 IDoc WPUUMS01: after to inbound processing
70. WPUWBW
POS interface: Upload goods movements
- WPUE0002 EXIT_SAPLWPUE_140 IDoc WPUWBW01: prior to update
- WPUE0002 EXIT_SAPLWPUE_141 IDoc WPUWBW01: processing user segment
- WPUE0002 EXIT_SAPLWPUE_142 IDoc WPUWBW01: prior to inbound processing
- WPUE0002 EXIT_SAPLWPUE_149 IDoc WPUWBW01: after to inbound processing
71. WVINVE
Store physical inventory / sales price revaluation
- WVFI0001 EXIT_SAPLWVFI_001 Inbound IDoc store phys. inv.: override Customizing
- WVFI0002 EXIT_SAPLWVFI_002 Inbound IDoc store phys. inv.: process customer segment
IDoc Outbound User Exits
72. ACCONF
Confirmation of IDoc processing from the application
- ACCID002 EXIT_SAPLACC2_040 IDOC ACCONF: Confirmation of processing in application
73. ACLPAY
Accounting: Inbound invoice
- ACCID002 EXIT_SAPLACC2_030 IDoc ACLPAY: Userexit for header in accounting document (outbound)
- ACCID002 EXIT_SAPLACC2_031 IDoc ACLPAY: Userexit for creditor line (outbound) in accounting document
- ACCID002 EXIT_SAPLACC2_032 IDoc ACLPAY: Userexit for general line (outbound) in accounting document
- ACCID002 EXIT_SAPLACC2_033 IDoc ACLPAY: Userexit for tax line (outbound) in accounting document
74. ACPJMM
Posting in accounting from materials management
- ACCID002 EXIT_SAPLACC2_020 IDoc ACPJOU: Userexit Userexit for GL posting header in accounting document
- ACCID002 EXIT_SAPLACC2_021 IDoc ACPJOU: Userexit Userexit for GL posting line in accounting document
75. ARTMAS
Create and change of material master (Retail)
- MGV00003 EXIT_SAPLMV01_003 Enhancement for article master IDoc: Create
76. BLAORD
Purchasing contracts
- MM06E001 EXIT_SAPLEINM_016 ALE distribution of contracts outbound enhancement for IDocs
- MM06E001 EXIT_SAPLEINM_017 ALE distribution of contracts outbound enhancement for IDocs
77. BLAREL
Purchasing contracts
- MM06E001 EXIT_SAPLEINM_003 Customer enhancements of data segment for outbound release documentation
78. COND_A
Conditions: master data for price determination
- VKOE0001 EXIT_SAPLVKOE_001 Condition Transmission: Derivation of Filter Object E1KOMG
- VKOE0001 EXIT_SAPLVKOE_002 Condition Transmission: Customer segments
79. CREMAS
Distribute vendor master
- VSV00001 EXIT_SAPLKD01_001 Outbound: Create vendor segments
80. DEBMAS
Customer master
- VSV00001 EXIT_SAPLVV01_001 Outbound: Create additional customer master segments
81. DELPKB
KANBAN call
- MPKD0001 EXIT_SAPLMPKD_001 User exit for control record KANBAN, outbound
- MPKD0001 EXIT_SAPLMPKD_002 User exit for EDI
82. DIRDEB
Preauthorized withdrawal
- FEDI0003 EXIT_SAPLIEDP_003 FI-EDI outgoing payments: Save PEXR segments (customer directory)
83. DOCMAS
Master document
- CVDS0001 EXIT_SAPLCVALE_002 Userexit for ALEDVS (DOCMAS outbound)
- CVDS0001 EXIT_SAPLCVALE_005 Userexit for filter (ALE outbound)
84. DOLMAS
Document-object links
- CVDS0001 EXIT_SAPLCVALE_004 Userexit for ALEDVS (DOLMAS outbound)
- CVDS0001 EXIT_SAPLCVALE_005 Userexit for filter (ALE outbound)
85. FIDCC1
Send entire FI documents (user exit 003/4)
- F050S001 EXIT_SAPLF050_001 IDoc outbound: fill user-defined IDoc segment
- F050S002 EXIT_SAPLF050_003 FIDCC1 IDoc outbound: Change data / do not send
- F050S004 EXIT_SAPLF050_007 IDoc outbound: change complete IDoc / do not send
86. FIDCC2
Send entire FI documents (user exit 005/6)
- F050S001 EXIT_SAPLF050_001 IDoc outbound: fill user-defined IDoc segment
- F050S003 EXIT_SAPLF050_005 FIDCC2 IDoc outbound: Change data / do not send
- F050S004 EXIT_SAPLF050_007 IDoc outbound: change complete IDoc / do not send
- F050S001 EXIT_SAPLF050_001 IDoc outbound: fill user-defined IDoc segment
87. FIDCMT
Sending single items for FI-GL
- F050S004 EXIT_SAPLF050_007 IDoc outbound: change complete IDoc / do not send
88. FIPAYM
Payment data
- FIPAYM01 EXIT_SAPLF11A_001 USER-EXIT: message type FIPAYM, header data, outbound
- FIPAYM01 EXIT_SAPLF11A_002 USER-EXIT: message type FIPAYM, reference data, outbound
- FIPAYM01 EXIT_SAPLF11A_003 USER-EXIT: message type FIPAYM, bank data, outbound
- FIPAYM01 EXIT_SAPLF11A_004 USER-EXIT: message type FIPAYM, GL data, outbound
- FIPAYM01 EXIT_SAPLF11A_005 USER-EXIT: message type FIPAYM, partner data, outbound
89. FIROLL
General ledger rollup for FI-GL (delta f. line items FIDCMT)
- F050S001 EXIT_SAPLF050_001 IDoc outbound: fill user-defined IDoc segment
90. GSVERF
Cred. memo procedure
- MRMN0001 EXIT_SAPLMRMN_001 Outbound IDoc for ERS/consignment settlement
91. HRMD_A
HR: Master data and organizational data (appl. system)
- RHALE001 EXIT_SAPLRHA0_001 HR-CA: ALE outbound processing: Enhancement for receiver
- RHALE001 EXIT_SAPLRHAL_001 HR-CA: ALE outbound processing: Change IDoc
- RHALE001 EXIT_SAPLRHAL_003 HR-CA: ALE outbound processing: conversion info type / segment
92. INFREC
Purchasing info record
- MMAL0003 EXIT_SAPLMEAO_002 ALE purchasing info record distribution: outbound processing
93. INVOIC
Invoice / Billing document
- LVEDF001 EXIT_SAPLVEDF_001 User_Exit controll data IDoc_Output_Invoic
- LVEDF001 EXIT_SAPLVEDF_002 User_Exit customer enhancement of segments outbound invoice
- LVEDF001 EXIT_SAPLVEDF_003 User_Exit to avoid reading package data
- LVEDF001 EXIT_SAPLVEDF_004 EDI Invoice: customer enhancement for reading additional data
94. KANBAN
KANBAN call
- MPKD0001 EXIT_SAPLMPKD_001 User exit for control record KANBAN, outbound
- MPKD0001 EXIT_SAPLMPKD_002 User exit for EDI
95. LIKOND
Listing conditions
- WSOR0001 EXIT_SAPLWSOE_001 Enhancement for assortments: outbound IDoc
96. MATMAS
Material Master
- MGV00001 EXIT_SAPLMV01_002 Enhancement for material master IDoc: Create
97. ORDCHG
Purchase order/order change
- MM06E001 EXIT_SAPLEINM_001 Customer enhancements for control record: purchasing document, outbound
- MM06E001 EXIT_SAPLEINM_002 Customer enhancements to data segments, purchasing document, outbound
- MM06E001 EXIT_SAPLEINM_011 Final customer enhancement EDI purchase order outbound
98. ORDERS
Purchase order / order
- MM06E001 EXIT_SAPLEINM_001 Customer enhancements for control record: purchasing document, outbound
- MM06E001 EXIT_SAPLEINM_002 Customer enhancements to data segments, purchasing document, outbound
- MM06E001 EXIT_SAPLEINM_011 Final customer enhancement EDI purchase order outbound
99. ORDRSP
Purchase order / order confirmation
- MM06E001 EXIT_SAPLEINM_009 MM EDI ORDRSP: customer enhancements tolerances (quantities/ date/price)
- MM06E001 EXIT_SAPLEINM_014 MM EDI ORDRSP:enhancement price tolerances
- MM06E001 EXIT_SAPLEINM_015 MM EDI ORDRSP: enhancement change of vendor material
- SDEDI001 EXIT_SAPLVEDC_001 Customer enhancement for control record of order confirmation
- SDEDI001 EXIT_SAPLVEDC_002 Customer enhancement for data records of order confirmation
- SDEDI001 EXIT_SAPLVEDC_003 SD EDI ORDRSP: customer enhancement
- SDEDI001 EXIT_SAPLVEDC_004 SD EDI ORDRSP:customer enhancement for reading additional data
- SDEDI001 EXIT_SAPLVEDC_005 SD EDI ORDRSP: customer enhancement for configuration
- SDEDI001 EXIT_SAPLVEDC_006 SD EDI ORDRSP: customer enhancement for configuration structures
- SDEDI001 EXIT_SAPLVEDC_007 SD EDI ORDRSP: customer enhancement for header conditions
- SDEDI001 EXIT_SAPLVEDC_008 SD EDI ORDRSP: customer enhancement for item conditions
- WVFB0001 EXIT_SAPLWVFB_001 Customer exists for store order PO confirmation control seg.
- WVFB0001 EXIT_SAPLWVFB_003 Customer exists for store order PO confirmation data seg.
100. PAYEXT
Extended payment order
- FEDI0003 EXIT_SAPLIEDP_002 FI-EDI outgoing payments: Save PEXR segments (external payments)
- FEDI0004 EXIT_SAPLIEDP_901 FI-EDI outgoing payments: New partner house bank
- FEDI0004 EXIT_SAPLIEDP_902 FI-EDI outgoing payments: End of IDoc payment (VBLNR)
- FEDI0004 EXIT_SAPLIEDP_903 FI-EDI outgoing payments: End of partner house bank
101. PICKSD
Picking data confirmation to customer delivery
- VMDE0002 EXIT_SAPLVMDE_002 Shipping Interface: Message PICKSD (Picking, Outbound)
102. PRDCAT
Product Catalog
- WPCI0001 EXIT_SAPLWPCI_001 User exit for Product cat. IDoc outbound
103. PRDPOS
Product catalog item
- WPCI0001 EXIT_SAPLWPCI_001 User exit for Product cat. IDoc outbound
104. PRICAT
Price list / catalog
- VPRE0001 EXIT_SAPLVPRE_001 PRICAT outbound processing (MAMT AUSP MAW1)
- VPRE0001 EXIT_SAPLVPRE_002 PRICAT outbound processing (control record)
- VPRE0001 EXIT_SAPLVPRE_003 PRICAT outbound processing (IDoc segments)
105. PROACT
Stock and sales data
- WVMI0001 EXIT_SAPLWVMI_001 IDoc PROACT outbound: final action prior to sending
106. REMADV
Payment advice
- FEDI0003 EXIT_SAPLIEDP_001 FI-EDI: Outgoing pmnt advice - Create extension of segments/ new segments
107. REQOTE
Inquiry
- VEDE0001 EXIT_SAPLVEDE_001 Customer enhancement for control record of outbound quotation
- VEDE0001 EXIT_SAPLVEDE_003 SD EDI REQOTE: customer enhancement
- VEDE0001 EXIT_SAPLVEDE_002 Customer enhancement for data records of outbound quotation
- VEDE0001 EXIT_SAPLVEDE_004 SD EDI REQOTE: customer enhancement for reading additional data
- VEDE0001 EXIT_SAPLVEDE_005 SD EDI REQOTE: customer enhancement for configuration
- VEDE0001 EXIT_SAPLVEDE_006 SD EDI REQOTE: customer enhancement for configuration structures
- VEDE0001 EXIT_SAPLVEDE_007 SD EDI REQOTE: customer enhancement for header conditions
- VEDE0001 EXIT_SAPLVEDE_008 SD EDI REQOTE: customer enhancement for item conditions
108. SRCLST
Source List
- MMAL0001 EXIT_SAPLMEAO_001 ALE source list distribution: outbound processing
109. SRVMAS
Master data service master
- BASO0001 EXIT_SAPLBASO_001 Enhancement: service master, check standard service catalog
- BASO0001 EXIT_SAPLBASO_002 Userexit IDoc service master: receiver determination
110. SYPART
Partner profiles
- SIDOC002 EXIT_SAPLEDI6_001 CA-EDI, Partner-IDoc: Exit after segment E1EDPP1
- SIDOC002 EXIT_SAPLEDI6_002 CA-EDI, Partner-IDoc: Exit after segment E1ADRM0
- SIDOC002 EXIT_SAPLEDI6_003 CA-EDI, Partner-IDoc: Final exit before sending
- SIDOC002 EXIT_SAPLEDI6_004 CA-EDI, Partner-IDoc: Exit after segment E1ADRP0
- SIDOC002 EXIT_SAPLEDI6_005 CA-EDI, Partner-IDoc: Exit after segment E1ADRE0
- SIDOC002 EXIT_SAPLEDI6_007 CA-EDI, Partner-IDoc: Exit after segment E1EDP13
- SIDOC002 EXIT_SAPLEDI6_008 CA-EDI, Partner-IDoc: Exit after segment E1EDP21
111. TPSDLS
Shipping planning system: Transfer delivery
- V56I0001 EXIT_SAPLV56I_001 IDoc TPSDLS: Modification of delivery header group
- V56I0002 EXIT_SAPLV56I_002 IDoc TPSDLS: Modification of delivery item group
- V56I0003 EXIT_SAPLV56I_003 IDoc TPSDLS: Modification of package data group
- V56I0004 EXIT_SAPLV56I_004 IDoc TPSDLS: Modification of entire IDoc
- V56I0005 EXIT_SAPLV56I_005 IDoc TPSDLS: Modif. of delivery items relevant to shipment
- V56I0006 EXIT_SAPLV56I_006 IDOC TPSDLS: User-defined determ. for location substitution
- V56I0020 EXIT_SAPLV56I_020 IDoc control record modification in interface SD-TPS
112. WBBDLD
Assortment list: Material data
- WBBE0001 EXIT_SAPLWBBI_001 Modification of replenishment list IDoc
113. WMCATO
Reversal/Reversal request for transfer order
- MWMIDO02 EXIT_SAPLLIDO_002 Customer enhancement for IDoc WMCAID01
114. WMINVE
Inventory count input
- MWMIDO04 EXIT_SAPLLIDO_004 Customer enhancement for IDoc WMIVID01
115. WMRREF
Release reference number
- MWMIDO03 EXIT_SAPLLIDO_003 Customer enhancement for IDoc WMRRID01
116. WMTORD
Transfer order
- MWMIDO01 EXIT_SAPLLIDO_001 Customer enhancement for IDoc WMTOID01
117. WP_EAN
POS interface: Upload / Download EAN assignments
- WPDA0001 EXIT_SAPLWPDA_003 POS interface: Modification of IDoc data for EAN references
118. WP_PER
POS interface: Upload / Download person data
- WPDA0001 EXIT_SAPLWPDA_008 POS interface: Modification of IDoc data for person related data
- WPDA0001 EXIT_SAPLWPDA_013 POS interface: Add. Change pt. Analysis for WP_PER
119. WP_PLU
POS interface: Upload / Download material master
- WPDA0001 EXIT_SAPLWPDA_002 POS interface: Modification of IDoc data for material master
- WPDA0001 EXIT_SAPLWPDA_009 POS interface: Add. Change pt. Analysis for WP_PLU
120. WPDCUR
POS interface: Download exchange rates
- WPDA0001 EXIT_SAPLWPDA_006 POS interface: Modification of IDoc data for exchange rates
121. WPDNAC
POS interface: Download products
- WPDA0001 EXIT_SAPLWPDA_005 POS interface: Modification of IDoc data for follow-on items
- WPDA0001 EXIT_SAPLWPDA_011 POS interface: Add. Change pt. Analysis for WPDNAC
122. WPDSET
POS interface: Download set assignments
- WPDA0001 EXIT_SAPLWPDA_004 POS interface: modification of IDoc data for set assignments
123. WPDSET
POS interface: Download set assignments
- WPDA0001 EXIT_SAPLWPDA_010 POS interface: Add. Change pt. Analysis for WPDSET
124. WPDTAX
POS interface: Download tax rates
- WPDA0001 EXIT_SAPLWPDA_007 POS interface: modification of IDoc data for taxes
125. WPDWGR
POS interface: Download material group master
- WPDA0001 EXIT_SAPLWPDA_001 POS interface: Modification of IDoc data for material groups
- WPDA0001 EXIT_SAPLWPDA_012 POS interface: Add. Change pt. Analysis for WPDWGR
126. WPUBON
POS interface: Upload sales documents (compressed)
- WPUE0002 EXIT_SAPLWPUE_102 IDoc WPUBON01: prior to update
127. WTADDI
Additionals
- WTAD0001 EXIT_SAPLWTIP_001 Enhancements to Additionals IDoc
128. WTADDI_CVB1
Additionals w/o 06
- WTAD0001 EXIT_SAPLWTIP_001 Enhancements to Additionals IDoc

SAP R/3 форум ABAP консультантов View topic - IDoc User Exit List

SAP123 | How to setup and use SAP

2010-02-24T14:16:00.001-08:00

Serial Numbers and materials

By Willem Hoek

Serialization is a way to keep track of individual items (material masters). When processing transactions, example Goods Receipt, Physical Inventory, etc.. you don't just type in material and quantity but also the serial numbers of the individual items. Serial numbers is a unique number that identify an item. Example if quantity is 2, one need to indicate serial numbers of the two items. A report is available to show all movements for a spesific serial number.
Lets go through a simple example to do a Physical Inventory posting on a material where we activate serial numbers.
Setting up -- Master data

A material is activated in Plant / Data Storage 2 view of material master. Field MARC-SERNP .The options (serialization profiles) are set up in configuration and define how it will be used (see below).

Using it in transactions

Lets look an an Inventory Management transaction for this material, transaction MI10 to do a stock adjustment and see where the serial numbers are used.

For this material, serialization is active, so the system force you to enter the serial numbers of the items, in this case the quantity was 2, therefore 2 serial numbers

Lets look at stock overview -- tcode mmbe and see if the serial numbers are visible.

Showing all the serial numbers

Double clicking on the serial number take you to transaction IQ03 -- serial number per material.

History of all inventory management transactions related to this serial number are visible by hitting the 'History' button

Setting up -- Configuration
IMG Menu: Sales and Distribution > Basic Functions > Serial Numbers > Determine Serial Number Profile - tcode OIS2

For every profile, one needs to specify the area in SAP where it will be used and how it will be used.

Serial number usage:
01 - None
02 - Optional
03 - Obligatory
04 - Automatic
Equipment required indicates if a equipment is required.
01 - Proposal without equipment
02 - always with equipment
SAP version used for this post: SAP ECC (ERP Central Component) 5.0

SAP123 | How to setup and use SAP

Handling differences in Purchase Order, Goods Receipts and Vendor Invoice Prices

2010-02-24T09:23:00.000-08:00

Handling differences in Purchase Order, Goods Receipts and Vendor Invoice Prices

What is the procedure to adopt in case of the following situations when they arise? (FOR SAP 4.6C version)

First situation
1)
a) PO LINE ITEM NET PRICE = US$100

b) The item is goods receipted with a price of US$110. Assume the difference of US$10 is because of tax caluculated by the system (for example)

c) Vendors sends an Invoice for this item at the price of US$85 (US$80 PO line item price + US$5 tax).

So in this case, the Invoice price is lower than the PO net price which is US$100.
So for this type of situation what is the procedure to adopt to post the invoice in the system.
Is it that the first the goods receipt needs to be reversed and then change or update the PO line item net price with US$80(for example) and then do the goods receipts and then do the invoice receipt?

If this procedure is correct and what happens if vendors invoice price is lower than the origianl PO line item net price (as described in this case), whether the system blocks the invoice in this case or not?

Or is it that the goods receipt need not be reversed and just post the invoice with the new price and change the PO price with the new vendor invocied price?

When is that the price in the info record needs to be changed?

Second situation
2) What is the procedure to adopt when the vendor's invoice price is greater than PO line item price?

Basically, I am just looking for the correct procedures to adopt in both of these cases like in what sequences,(like what is the first step and what is the second step) with what steps to follow.

What to do procedurally - how to post an invoice with differing value than PO and/or GR and what to do if an invoice blocks, etc in both the cases like when the vendor invoice price is less than the PO price (line item net price plus tax) and one more, I need to know is in this case will the invoice gets blocked upon invoice posting when the vendor price is low.

Similarly in the second case what to do procedurally when the invoice price is more than the PO price (Line item net price +tax)?

Whatever tolerances you have set for over or under invoice will determine if any blocks occur (this covers both your first and second examples). (Transaction code: OMR6)

When the clerk enters the invoice the system will note that the invoice is going to block but will not stop it from being posted. (Transaction: MIRO)

Procedurally, the buyer checks blocked invoices and resolves the block be either:

1. Changing the PO price to match the invoice and then the invoice should unblock (either automatically if you have it set up that way, or the buyer can release the block) or

2. Buyer can dump the block without changing the PO price (info record price history is not updated in this case because PO price wasn't changed).

In either case, if you have your materials being valuated at GR and then at IR, the invoice will revalue the material so there is not really a need to reverse the GR to change the PO price and then reenter the GR.

The transaction code for viewing blocked invoices (and releasing them) is MRBR.

payment block, - Toolbox for IT Groups

2010-02-23T09:44:00.001-08:00

payment block,

Asked by gangadhar.redd... on 4/19/2004 5:59 AM

Hi,
We have 3 invoices which are blocked for payment due to Schedule date
variance. While doing MRBR these document does not show up to release for
payment, Not able to understand what is the problem. System shows the
message "M8 658 :- no blocked invoices found". There is note 679788 on
message # M8 657. can I implement it in this situation? Would it give the
expected results!!

payment block, - Toolbox for IT Groups

ONE TIME VENDOR

2010-02-22T08:50:00.001-08:00

one time vendor'. what is the benefit of create on 'ome time vendor'. please explain.

--------

One time vendor is used for occasional or rare purhasing from a particular vendor.

For example you are purchasing a particular material few times a year and you have more materials and many vendors ( > 50).

You no need to create all the vendors in the system, you can simply create one time vendor and it will serve the purpose of >50 VMR.

Whenever you use the one time vendor in applications like RFQ,PO,Contract, you must maintain the address manually

And during invoice verification you must input the bank details.

Hope it helps

Thanks/karthik

-------

One time vendor means a vendor from which normally we dont procure material frequently. May be once in a year or may be for the purpose of Quotation we can create one time vendor.

Creating one time vendor is the same process as creating regular vendor (XK01/FK01), the only difference will be Vendor Account Group. For one time vendor there will be saperate vendor account group so at the time of vendor create it will require minimum vendor information.

You need to maintain vendor address and other relevent accounting data at the time of PO and IR.

If you want to make one time vendor for regular vendor you can change the vendor account group and maintain the additional data as required for regular vendor.

Regards,
Nani.

----------

One Time Vendor is normal type of vendor but with different account group(account grp classifies vendor master).
The beauty of one time vendor is that you can create a vedor group(one time vendor code) and when you are using this vendor code in Purchase order and during Inv receipt,you can put the address of the vendor you desire.

This concept is usually used in repair scenario,where one is quite not sure to whom he is goinig to give the order.Eg If I want to repair an motor,It is very difficult to decide the source and here come the ONE TIME VENDOR.
When you create an order with one time vendor befor saving the purchase order system asks you address of the vendor to be maintained.

Hope it is usefull to you......

--------

the purpose is to avoid data redundancy as we use the account group of one time the vendor specifc fileds will become greyed out ,this is becuase we may occasionally buy from that vendor for those vendor we may not required to maintain a master data in taht case we will be storing large number of datas which we may occasinally use.

---------

here i am giving one example of business process , one telecom comapny is there and sold out some public booths , after some days they want to return the public booths to the telecom company, in this case the telecom company maintained one one-time vendor and will raise POs with different booth owners addresses and receive that booths and pay the amount,
in the above case vendor code is same for all POs and deliver to different places,

-------------

One time Vendor is one which is used very rarely . It differs from the regular vendor in few cases:
1. Vendor account group changes
2.doesnt contain Vendor address and Bank details.

When there has to be many vendor master records created for one time use or very rare purpose , u will alwaz create this type of one time vendor where as u dont have to give all the Vendor related details. So u specially select the one time vendor account group and create this type of vendor.

Hope this helps u.

-----------

one time vendors are useful to not blow up your vendor masterdata.

In a lot of companies masterdata maintaince is centralized and setting up a new vendor master cost money.

So if you legally need to put in an invoice on the vendor because of e.g. VAT requirements or you want to pay it by automatic payment but you are sure you never use the masterdata again, one-time (CPD) vendor are a good solution.

--------------------

mySAP FI - Purpose of One Time Vendor / Customer

2010-02-22T08:26:00.001-08:00

What is the treatment of one time customer / vendor accounts in SAP?

One time customer / vendor accounts in SAP means they are account groups for customer/vendor and where in only the general data of the customer / vendor are stored instead of maintaining the bank data and other company code data that are relevant for other account groups which are useful for long run purposes.

As you know everything that is entered in SAP is saved in some TABLE. Now the customer & vendor master is such a table which holds vast amount of data.

The business secenario where the vendor or customer which are being in system only for 1 transaction, it is not advisable to have all the data maintained in main master.

Therefore SAP has provided with the feature of One time vendor / customer wherein in the document entry stage only you have to enter the name, addres and other details of the vendor/customer.

The data, as far as I know' remains at doc level and does not goes to master tables.

Tips by Santosh Kumar Agarwal

What is difference between vendor and one time vendor and what purpose to create one time vendor and what are required field to fill in vendor and one time vendor? - Navas

One time vendors are those who are not frequent vendors. Company will be using those vendors very rarely, maybe once in a life time. SAP is giving a special category for those type of vendors. Normal vendors will have separate Master Data which will have their address, country, bank account, terms of payment, payment methods, etc.

Whereas there will not be such records kept in Master data for those one time vendors. This way you will reduce the data base size. There will be one vendor master record named as one time vendors and will have the check box ticked while creating this record. Country field is mandatory when creating a normal vendor master (sap standard) whereas it will not be in case of one time vendor.

When you post a document to this vendor (One time vendor), it will prompt you to fill the name address and all the required fields at the document level.

mySAP FI - Purpose of One Time Vendor / Customer

System Task: Create a One-Time Vendor Master Record

2010-02-22T08:22:00.001-08:00

System Task: Create a One-Time Vendor Master Record

Overview

Use this transaction to create a new One-Time Vendor Master Record. A one-time vendor includes:

a vendor who produces a unique service or product

travel advances and reimbursements

a non-purchase order vendor

Menu Path
From the SAP R/3 Screen, select the path:

Logistics >> Materials management >> Purchasing >>

(new menu) Master data >> Vendor >> Central >> Create

Fast Path
At the Command Line, enter:

/NXK01

Create Vendor: Initial Screen

Key Fields (Complete or Review)

Vendor

To create a vendor master for a different purchasing organization, enter the vendor account number. Otherwise, leave blank.

Company code

Enter CUR for MIT.

Purch. organization

Enter one of the following purchasing organization codes:

GPO General Purchasing

SUB Subcontracts

Account group

Enter CPD to indicate the MIT One-time vendor account group.
To tie the one-time vendor master to a reference vendor, enter the following fields, located in the Reference Box:

Note: The information entered for a reference vendor defaults to the One-Time Vendor Master Record being created.

Vendor

If using a reference vendor, enter the reference vendor number. Otherwise, leave blank.

(F4) to access a matchcode.

Company code

If using a reference vendor, enter CUR to indicate MIT. Otherwise, leave blank.

Purch. organization

If using a reference vendor, enter one of the following purchasing organization codes. Otherwise, leave blank.

GPO General Purchasing

SUB Subcontracts

Next Step...

(ENTER) to access the Create Vendor: Address Screen.

Create Vendor: Address Screen

Key Fields (Complete or Review)

Name

To indicate that this is a one-time vendor, enter ONE-TIME VENDOR.

Search term

To indicate that this is a one-time vendor, enter ONETIME.

Country

Enter the vendor's abbreviated country name.

(F4) to access the full list.

Language

Enter E for English.

Next Step...

(ENTER) to access the Create Vendor: Accounting info. Screen.

Create Vendor: Accounting info. Screen

Key Fields (Complete or Review)

Reconcil. acct

Enter 200010 to indicate the AP Reconciliation Account for Vendors as the vendor's G/L reconciliation account.

Sort key

Enter the key indicating the layout rule for the allocation field in the document item if known.

(F4) to access the full list.

Minority indic.

Enter the code indicating whether the vendor is a small or minority-owned business.

(F4) to access the full list.

Prev. acct no.

Enter the vendor's previous VAPS number if known.

Next Step...

(ENTER) to access the Create Vendor: Payment Transactions Screen.

Create Vendor: Payment Transactions Screen

Key Fields (Complete or Review)

Payment terms

Enter ZB00 to indicate the terms of payment being Within 30 Days Due Net.

(F4) to access the full list.

Chk double inv.

Click the box to have the system automatically check for duplicate invoices when posting is made to the vendor account.

Payment methods

Enter C to indicate the method used to pay the vendor is by Check.

Payment block

Enter the block for payment code for the vendor account if known.

(F4) to access the full list.

Next Steps...

(ENTER) to access the Create Vendor: Correspondence Screen.

(ENTER) to access the Create Vendor: Purchasing data Screen.

Create Vendor: Purchasing data Screen

Key Fields (Complete or Review)

Order currency

Enter USD to indicate US dollar as the purchase order currency.

Terms of payment

Enter ZB00 to indicate the terms of payment being within 30 days due net.

(F4) to access a matchcode.

Salesperson

Enter the name of the responsible salesperson at the vendor's office if known.

Telephone

Enter the salesperson's telephone number if known.

Required Selection
Click the box beside one or more of the following fields in the Control Data Box:

GR-based inv. verif.

To indicate GR-based invoice verification.

Automatic PO

To indicate that purchase orders are to be generated automatically from purchase requisitions if the requisition has been assigned to the vendor.

Next Step...

(F11) to save the One-Time Vendor Master Record. The Create Vendor: Initial Screen reappears, and a message indicating that the vendor master has been created appears in the System Message Line at the bottom of the screen.

Copyright © 1996, Massachusetts Institute of Technology. All rights reserved.

System Task: Create a One-Time Vendor Master Record

Posting more than 999 records through BAPI

2010-02-21T12:19:00.001-08:00

Posting more than 999 records through BAPI
Welcome Guest

View Comments (0) Attachments (3) Info

Additional Features

Added by Krishna Chauhan , last edited by Craig Cmehil on Dec 28, 2009 (view change)

Labels:

abap, tutorial

Add Labels

Enter labels to add to this page:

Tip: Looking for a label? Just start typing.

Introduction: There are a number of scenarios when we found our BAPI does not post/check records more than 999 line items. Actually there is a limitation in BAPI where we can't post more than 999 records. This small piece of code will serve our purpose.
Suppose our XL file contains thousand of records & we have to check/post using BAPI in a bunch of 950 records.
We need to upload the data of XL to our internal table, let's say we have uploaded the records to internal table   ITAB_INDATA.

PERFORM POST_DOCUMENT .

FORM        POST_DOCUMENT .

DATA: V_LINES TYPE I,

              V_LINES1 TYPE I,

             COUNT(3)   TYPE N.*----declaration of internal tables used in BAPI

DATA: DOC_HEADER LIKE BAPIACHE09 OCCURS 0 WITH HEADER LINE,

            DOC_ITEM   LIKE BAPIACGL09 OCCURS 0 WITH HEADER LINE,

            DOC_VALUES LIKE BAPIACCR09 OCCURS 0 WITH HEADER LINE,

            CUSTOMER   LIKE BAPIACAR09 OCCURS 0 WITH HEADER LINE,

            VENDOR     LIKE BAPIACAP09 OCCURS 0 WITH HEADER LINE,

           CHECK_RETURN LIKE BAPIRET2 OCCURS 0 WITH HEADER LINE,

           OBJTYP TYPE AWKEY.

DATA: V_BAL   TYPE P DECIMALS 4,

               V_BAL1 TYPE P DECIMALS 4,

               V_INDEX LIKE SY-TABIX.*---set the counter to '0' which will calculate the number of records

COUNT = 0.

CLEAR: ITAB_INDATA. *---Calculating the number of records in internal table

DESCRIBE TABLE ITAB_INDATA LINES V_LINES.*----Logic to be implemented inside the internal table

LOOP AT ITAB_INDATA.    *----Clearing the internal tables before appending data
    CLEAR: DOC_HEADER[], DOC_ITEM[], CUSTOMER[], VENDOR[], DOC_VALUES[].

    CLEAR: LWA_INPUT_FILE.*----Here we are filling the structure and internal tables corresponding to Transaction Number field in our internal table

AT NEW TNO.

      LOOP AT ITAB_INDATA INTO LWA_INPUT_FILE WHERE TNO = ITAB_INDATA-TNO.* Fill Document Header

        DOC_HEADER-USERNAME = SY-UNAME.

        DOC_HEADER-COMP_CODE = 'BP01'.

        DOC_HEADER-HEADER_TXT = LWA_INPUT_FILE-BKTXT.

        DOC_HEADER-REF_DOC_NO = LWA_INPUT_FILE-XBLNR.

        DOC_HEADER-DOC_DATE   = LWA_INPUT_FILE-DDATE.

        DOC_HEADER-PSTNG_DATE = LWA_INPUT_FILE-PDATE.

        DOC_HEADER-DOC_TYPE   = LWA_INPUT_FILE-BLART.

        ADD 1 TO COUNT. ** Fill Document Item

        MOVE COUNT TO DOC_ITEM-ITEMNO_ACC.

        MOVE COUNT TO DOC_VALUES-ITEMNO_ACC.

          DOC_ITEM-GL_ACCOUNT = LWA_INPUT_FILE-GLACC.

          DOC_ITEM-PSTNG_DATE = LWA_INPUT_FILE-PDATE.

          DOC_ITEM-DOC_TYPE   = LWA_INPUT_FILE-BLART.

           DOC_ITEM-PROFIT_CTR = LWA_INPUT_FILE-PC.

           DOC_ITEM-ALLOC_NMBR = LWA_INPUT_FILE-ASSGN.

           DOC_ITEM-ITEM_TEXT = LWA_INPUT_FILE-TEXT.

           DOC_ITEM-COSTCENTER = LWA_INPUT_FILE-CC.

           DOC_ITEM-ACCT_TYPE = LWA_INPUT_FILE-ACTYP.

           DOC_ITEM-COMP_CODE = 'BP01'.

          CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'

            EXPORTING

              INPUT = DOC_ITEM-GL_ACCOUNT

            IMPORTING

              OUTPUT = DOC_ITEM-GL_ACCOUNT.
          CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'

            EXPORTING

              INPUT = DOC_ITEM-COSTCENTER

            IMPORTING

              OUTPUT = DOC_ITEM-COSTCENTER.
          CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'

            EXPORTING

              INPUT = DOC_ITEM-PROFIT_CTR

            IMPORTING

              OUTPUT = DOC_ITEM-PROFIT_CTR.          APPEND DOC_ITEM.
          CLEAR DOC_ITEM.
          MOVE COUNT TO VENDOR-ITEMNO_ACC.

          VENDOR-VENDOR_NO = LWA_INPUT_FILE-GLACC.

          VENDOR-ALLOC_NMBR = LWA_INPUT_FILE-ASSGN.

          VENDOR-ITEM_TEXT = LWA_INPUT_FILE-TEXT.
          CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'

            EXPORTING

              INPUT = VENDOR-VENDOR_NO

            IMPORTING

              OUTPUT = VENDOR-VENDOR_NO.

          APPEND VENDOR.

          CLEAR VENDOR.

          MOVE COUNT TO CUSTOMER-ITEMNO_ACC.

          CUSTOMER-CUSTOMER   = LWA_INPUT_FILE-GLACC.

          CUSTOMER-ALLOC_NMBR = LWA_INPUT_FILE-ASSGN.

          CUSTOMER-ITEM_TEXT = LWA_INPUT_FILE-TEXT.

          CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'

            EXPORTING

              INPUT = CUSTOMER-CUSTOMER

            IMPORTING

              OUTPUT = CUSTOMER-CUSTOMER.

          APPEND CUSTOMER.

          CLEAR CUSTOMER. * Fill Document Value.

        DOC_VALUES-CURRENCY_ISO = 'USD'.

        DATA: NUM TYPE P DECIMALS 2.

        CLEAR NUM.*---in case of Credit amount available

          DOC_VALUES-AMT_DOCCUR = LWA_INPUT_FILE-CRAMT * -1.*---in case of Debit amount available

          DOC_VALUES-AMT_DOCCUR = LWA_INPUT_FILE-DRAMT.        APPEND DOC_VALUES.
        CLEAR DOC_VALUES.         V_LINES1 = V_LINES1 + 1.                "Counting line no
        READ TABLE ITAB_INDATA INDEX V_INDEX.

        IF ITAB_INDATA-DRAMT <> SPACE.

          CLEAR V_BAL.          "clear when found debit amount

          V_BAL1 = ITAB_INDATA-DRAMT.

          V_BAL = V_BAL + V_BAL1.

        ENDIF.

        IF SY-SUBRC = 0.

          IF ITAB_INDATA-CRAMT <> SPACE.

            V_BAL1 = ITAB_INDATA-CRAMT * -1.

            V_BAL = V_BAL + V_BAL1.

          ENDIF.

        ENDIF.    *----V_LINES contains total no of records in internal table
        IF V_LINES >= 950.

          IF V_LINES1 >= 950

                        AND V_BAL = 0.*---call bapi

              PERFORM CHECK_BAPI.

           ENDIF.   "IF CHECK <> 'X'.*---refreshing tables for storing another chunk of records

            REFRESH: DOC_ITEM, CUSTOMER, VENDOR, DOC_VALUES.

            clear COUNT.

            V_LINES = V_LINES - V_LINES1.

            CLEAR: V_LINES1, V_BAL.   "clearing balance & line counts

            CONTINUE.

          ELSE.

            CONTINUE.

        ENDIF.

      ENDLOOP.*----In case records less than 950

      IF V_LINES < 950

                 and V_LINES <> 0. "avoiding if remaining records = 0.*---call bapi

            PERFORM CHECK_BAPI.*---refreshing tables for storing another chunk of records

            REFRESH: DOC_ITEM, CUSTOMER, VENDOR, DOC_VALUES.

          ENDIF.   "IF CHECK <> 'X'.

    ENDAT.

ENDLOOP.

ENDFORM.                    " POST_DOCUMENT
FORM CHECK_BAPI .

CALL FUNCTION 'BAPI_ACC_DOCUMENT_CHECK'

    EXPORTING

      DOCUMENTHEADER          = DOC_HEADER

    TABLES

     ACCOUNTGL               = DOC_ITEM

     ACCOUNTRECEIVABLE       = CUSTOMER

     ACCOUNTPAYABLE          = VENDOR

     CURRENCYAMOUNT          = DOC_VALUES

      RETURN                  = CHECK_RETURN    .*----If CHECK_RETURN contains Success result then post documents using

CALL FUNCTION 'BAPI_ACC_DOCUMENT_POST'

    EXPORTING

      DOCUMENTHEADER    = DOC_HEADER

    IMPORTING

      OBJ_KEY           = OBJTYP

    TABLES

      ACCOUNTGL         = DOC_ITEM

      ACCOUNTRECEIVABLE = CUSTOMER

      ACCOUNTPAYABLE    = VENDOR

      CURRENCYAMOUNT    = DOC_VALUES

      RETURN            = RETURN.

*---If no error found commit BAPI   'BAPI_TRANSACTION_COMMIT'

ENDFORM.                    " CHECK_BAPI

When the documents get posted the 'BAPI_ACC_DOCUMENT_POST' will generate an document no.

We can pass that document number to FB03 Transaction to check out the posted documents.

SAP Community Network Wiki - ABAP Development - Posting more than 999 records through BAPI

BAPI_ACC_GL_POSTING_POST

2010-02-20T14:55:00.001-08:00

Author: pradeepchoudhari
REPORT zpradeep_gl_posting.
DATA:
* Structure for document header
g_docheader LIKE bapiache08,
* Table and header for G/L Account Line Items
gi_accountgl TYPE STANDARD TABLE OF bapiacgl08,
g_accountgl LIKE bapiacgl08,
* Table and header for Line Item Currency Fields
gi_amount TYPE STANDARD TABLE OF bapiaccr08,
g_amount LIKE bapiaccr08,
* Return
gi_return TYPE STANDARD TABLE OF bapiret2,
g_return LIKE bapiret2.
START-OF-SELECTION.
*---------------------------------------------------------
* HEADER DATA
*
* OBJ_TYPE Objekttypes can be found in table TTYP
* OBJ_KEY Seems that you can use any value
* OBJ_SYS Logical system. Logical ystems can be found in
* table TBDLS. If there is no logical system assigned
* to the client, assign it this way:
*
* Transaction: SPRO
* - Basis components
* - Application Link Enabling (ALE)
* - Sending and receiving systems
* - Logical systems
* - Define logical system
* - Assign client o logical system
*
*
*---------------------------------------------------------
g_docheader-obj_type = 'BKPFF'.
g_docheader-obj_key = '1'.
g_docheader-obj_sys = 'B3TCLNT800'.
g_docheader-username = sy-uname.
g_docheader-header_txt = 'BAPI test'.
g_docheader-comp_code = '1000'.
g_docheader-doc_date = sy-datum.
APPEND g_amount TO gi_amount.
*---------------------------------------------------------
* LINE ITEMS
*---------------------------------------------------------
* Item 1
g_accountgl-itemno_acc = '0000000001'.
g_accountgl-gl_account = '0000192600'.
g_accountgl-pstng_date = sy-datum.
APPEND g_accountgl TO gi_accountgl.
* Item 2
g_accountgl-itemno_acc = '0000000002'.
g_accountgl-gl_account = '0000192600'.
g_accountgl-pstng_date = sy-datum.
APPEND g_accountgl TO gi_accountgl.
*---------------------------------------------------------
* CURRENCY AND AMOUNT
*---------------------------------------------------------
* Item 1
g_amount-itemno_acc = '0000000001'.
g_amount-currency = 'EUR'.
g_amount-amt_doccur = 5000.
APPEND g_amount TO gi_amount.
* Item 2
g_amount-itemno_acc = '0000000002'.
g_amount-currency = 'EUR'.
g_amount-amt_doccur = -5000.
APPEND g_amount TO gi_amount.
END-OF-SELECTION.
* Call the BAPI function
CALL FUNCTION 'BAPI_ACC_GL_POSTING_POST'
EXPORTING
documentheader = g_docheader
* IMPORTING
* OBJ_TYPE =
* OBJ_KEY =
* OBJ_SYS =
TABLES
accountgl = gi_accountgl
currencyamount = gi_amount
return = gi_return
* EXTENSION1 =
.
LOOP AT gi_return INTO g_return.
WRITE: / g_return-message.
ENDLOOP.

SAP R/3 форум ABAP консультантов View topic - BAPI_ACC_GL_POSTING_POST

SAP Community Network Forums: BAPI 'BAPI_ACC_GL_POSTING_POST' ...

2010-02-20T14:37:00.001-08:00

BAPI_ACC_GL_POSTING_CHECK

CALL FUNCTION 'BAPI_ACC_GL_POSTING_CHECK'
EXPORTING
documentheader = w_documentheader
TABLES
accountgl = it_accountgl
currencyamount = it_currencyamount
return = it_return.

Populate the corresponding tables with the data you have.
For the Date do convert it.
PERFORM convert_date USING it_header-bldat
CHANGING w_documentheader-doc_date.

w_documentheader-comp_code = 'z998'
w_documentheader-doc_type = 'SA'
"and fill the respective tables this way .

BAPI_ACC_GL_POSTING_POST

call function 'BAPI_ACC_GL_POSTING_POST'
exporting
documentheader = doc_header
IMPORTING
OBJ_TYPE = l_objtype
* OBJ_KEY =
* OBJ_SYS =
tables
accountgl = t_accountgl
currencyamount = t_curramt
return = t_return
* EXTENSION1 =

SAP Community Network Forums: BAPI 'BAPI_ACC_GL_POSTING_POST' ...

Payment Block

2010-02-16T05:00:00.001-08:00

Payment block R can come for various reasons like delivery schedule,terms of payment,quality reasons etc.
Use
You can block an invoice manually. You have two options for doing this when you enter the invoice:
You can block an invoice by entering an R in the field Payment block in the document header data.
You can block an item by selecting the M (manual blocking reason) field in the item list. When you post the invoice, the system automatically sets an R in the field Payment block in the vendor line of the accounting document. Manually blocked items are given the blocking reason Manual block (M).

================================================================================================================================================================================================

Re: Prevent removal of invoice verification paymt block in F

Guys, what the hell you are talking about? It's much more simple... Tr. OB27. the very right column - "not changeable". Blocking indicator R should have this tick (plus check box "manual payment block to be not ticked), all other blocking indicators which are supposed to be set/removed through FB02 - not ticked (along with check box "manual payment block ticked), it does the job.

================================================================================================================================================================================================

Invoice verification Error Message

Every time I try to do invoice verification in MM, I get the message below. PL tell me how I can resolve the issue. And also The amount you enter by default is alaways in USD, could we use any other Currency.
Error Msg --> You may only enter amount upto USD 10,000.00

Hi,
Go to SPRO > MM > Logistics Invoice Verification > Authorization Management > Define Tolerance Groups
Here check the following;
Amount per document
Amount per open item account item
Cash discount per line item
And increase the amount if you want
Here we do following activities;
1. By choosing Edit -> New entries, you create a new combination of tolerance group and company code.
2. To reach the allocation table on the detail screen, position the cursor on a line and choose Details. Enter the maximum permissible values for the tolerance group in the area "Upper limits for posting procedures".
The area "Permitted payment differences" is only important for employees in Financial Accounting.
SPRO > MM > Logistics Invoice Verification > Authorization Management > Assign User Tolerance Group > Here Assign a tolerance group to each user
If you don't want this message for the user then delete this user ID from this and then check

================================================================================================================================================================================================

Manual Payment Block

2010-02-16T04:57:00.001-08:00

You can remove payment block manually by following method aprat from MRBR:

In purchasing at the time of posting.

Go to :Logistics >> Material management >> Purchasing >> Purchase Order>> Follow-on Functions >> Logistics Invoice Verification >> EnterInvoice(MIRO)

Step 1
To remove a block at the time of posting, you must access the payment document (51XXXXXXXX) immediately after completing theposting. Click on Invoice document >> Display
The document you just posted will be displayed. Click on Following Documents.
A pop-up box listing the accompanying (system created documents) is displayed.
Click on Accounting document. The invoice document will be displayed.

Step 2
Double click on the vendor line item, which is the first line item to display the payment screen.
If this in an OTA Vendor, you will need to click on or hit enter when the Address screen appears
To remove the block, simply click on the change icon, this will open the Pmnt block field for change. Delete the R and click onto save the document.

2.In accounts payable after posting.
Accounting >> Financial Accounting >> Accounts Payable >> Document >> Change
To remove a block after posting, you must access the payment document (51XXXXXXXX) through Accounts Payable and remove the block.

At the Change document: Initial screen, enter the document number and press enter.
Double click on the vendor line item (line item 1) to display the payment screen.
If this in an OTA Vendor, you will need to click on or hit enter when the Address screen appears.

In the Pmnt block field, the R (Invoice verification) must be removed. To remove the block, simply delete the R in the Pmnt block filed and click on
to save the document.

MM-IV-LIV-MRBR Invoice Release in LIV Transaction MRBR

2010-02-14T16:35:00.001-08:00

Welcome Guest

Added by Guest , last edited by Guest on Jun 04, 2009 (view change)

Labels:

(None)

Add Labels

Enter labels to add to this page:

Tip: Looking for a label? Just start typing.

Content

Use and Overview

Before you can pay a blocked invoice, you must release it in a separate step. You do so by canceling the blocking indicator that was set when the invoice was posted.
Since the total invoice amount is to be paid and not individual invoice items, the blocking indicator is set in the vendor line of the accounting document. As a result, all the items in an invoice can only be released at the same time.
MR02: invoice release transaction for blocked invoices that were posted in CIV (MR01)
MRBR: invoice release transaction for blocked invoices that were posted in LIV
Releasing LIV blocked invoices that were posted before 4.6A: MR02 or MRBR if you first convert them with report RM08RBKPBLOCKED
two processes for releasing invoices for payment:
- Releasing Automatically
- Releasing Invoices Manually

Settle with transaction MBRR: selection

Move cash disc. Date:
- To specify when exactly an invoice is to be paid, you agree terms of payments with the vendor. These terms of payment contain the baseline date from which your cash discount period applies. If an invoice was blocked for payment for a long time, your cash discount deadline could expire. If you release this invoice, you can select the field Move cash discount date on the initial screen of the invoice release transaction and retain the agreed cash discount.
Canceled invoices are not taken into account.

Settlement with transaction MBRR: Releasing Automatically

Use
When you release invoices automatically, the system deletes all blocking reasons that no longer apply.
When all blocking reasons in an invoice are deleted, the system automatically releases the invoice.

Prerequisites
It is only possible to automatically release invoices if their blocking reasons are no longer valid. This can be the case for invoices blocked due to quantity, price, or schedule variance s, or due to quality inspection.
You can only use the function Release automatically for the blocking procedure Blocked due to variances.

Result
The system issues a list of the invoices released. The system will also release invoices for which a manual block was set in the document header if the blocking reasons in all items no longer apply.

Settlement with transaction MBRR: Releasing Manually

Deleting Blocking Reasons

Use
You can delete individual blocking reasons while processing a blocked invoice item.

Procedure

Place the cursor on the blocking reasons that you want to delete.
Choose Delete blocking reasons. The system highlights the deleted blocking reason in color.
Check your entries.
Choose Save changes.

Result
If there are other blocking reasons in this item or other items in the invoice, you receive a message
indicating that the selected blocking reason was deleted.
When you delete the last blocking reason in an invoice, the system automatically releases the invoice. The following message appears:
nn invoice(s) released

Releasing Invoices

Use
When you release an invoice, the system reverses the blocking indicator in the accounting document for the invoice. In the vendor line, the R in the field Payment block is deleted.

Procedure

Select the invoice document that you want to release. The system automatically selects all other items in the invoice since you cannot release individual items.
Choose !6 Release Invoice.jpg!Release invoice.
Check your entries.
Choose Save changes. The invoices selected are only released for payment when you save them.

Technical details: Database Structure

Database Structure of Incoming Invoice:

RBKP: Header data of an Incoming Invoice
RSEG: Item data (reference to a PO)
RBMA: Item data (reference to a material)
RBCO: Item data (Direct posting to G/L account)

Specialities of an Incoming Invoice blocked for payment:

There exists a record in the index table RBKP_BLOCKED (containing 10 fields for fast selection of blocked invoices)
Important field in RBKP_BLOCKED: Logistics payment block (MRM_ZLSPR) with possible values
- A Automatically blocked due to existence of blocking reasons
- S Stochastically blocked
- M Manual payment block set in header - no blocking reasons
In an automatically blocked invoice (MRM_ZLSPR = 'A') there is at least one blocking reason in RSEG / RBMA / RBCO:

Database structure of the FI follow-on document:
- First (vendor) BSEG Item: Payment Block is set (BSEG-ZLSPR = ‚R')
Attention: RBKP contains exactly the data the user has entered, so RBKP-ZLSPR is only filled when the user has entered a value. This means
- The field RBKP-ZLSPR is not necessarily set in the case of blocked invoices:
- The field RBKP-ZLSPR will never be changed in the Release process

Technical Details: RM08RELEASE - Overview Flow Logic

Technical Details: Debugging tips (1)

Why does MRBR not show an invoice as blocked for payment?

First check the corresponding database entries (RBKP_BLOCKED, first BSEG item: BSEG-ZLSPR)
Debugging: breakpoint on SELECT of RBKP_BLOCKED in RM08RELEASE:
...
START-OF-SELECTION.

* Selection from RBKP_BLOCKED -----------------------------------------*
SELECT * FROM rbkp_blocked INTO TABLE tab_rbkp_blocked
       WHERE    mrm_zlspr = f_mrm_zlspr
         AND    bukrs      IN so_bukrs
         AND    gjahr      IN so_gjahr
         AND    lifnr      IN so_lifnr
         AND    belnr      IN so_belnr
         AND    usnam      IN so_usnam
         AND    budat      IN so_budat
         AND    faell      IN so_faell
         AND    ekgrp      IN so_ekgrp.
...

Technical Details: Debugging tips (2)

Why does (does not) MRBR release an invoice automatically?

Check the prerequisites for releasing invoices automatically. Check if with processing option „release manually", blocking procedure „blocked due to variances" the blocking reason is white (~valid) or coloured (~not valid)

Why does MRBR show a blocking reason as valid (not valid)?

Check the IMG documentation of the corresponding tolerance key.
Debugging:
Put a breakpoint on:
RM08RELEASE form BLOCKING_REASON_VALIDITY_CHECK
Put another breakpoint on
function module: MRM_TOLERANCE_CHECK
(MRM_TOLERANCE_CHECK is executed e.g. in RM08RELEASE from function module MRM_BLOCK_REASON_VAL_CHECK_P which is called from BLOCKING_REASON_VALIDITY_CHECK for tolerance key PP.
MRM_TOLERANCE_CHECK is also the function module which -in general- determines whether an invoice is blocked for payment when you post it e.g. with MIRO)

Technical Details: RM08RELEASE - Summary

Transaction MRBR
Report RM08RELEASE
Works only for documents of LIV when they have a record in the index table RBKP_BLOCKED. Cancelled Invoices are not selected by MRBR because they do not have a RBKP_BLOCKED entry.
Selection Screen: like a usual report
List: ALV
Automatic Release in the background possible
Database update not immediately but after saving explicitly

Update of the Incoming Invoice

Deletion RBKP_BLOCKED
Deletion blocking reasons in RSEG if necessary
Update of FI follow-on document (Deletion BSEG-ZLSPR) via Accounting Interface (TRWPR-PROCESS = ‚PYMNTBLK')
- AC_PAYMENTBLOCK_CHECK

MM Tables

2010-02-09T12:59:00.001-08:00

Material Mnagement Tables

Written by anon

Material Management Tables

EINA purchasing Info record.

EINE Purchasing Info Record Purchasing Data.

MAKT Material description.

MARA General Material Data.

MARC Plant data for material

MARD Storage location Data for material.

MAST Material to BOM Link.

MBEW Material valuation

MKPF Header Material Document

MSEG Document segment material.

MVER Material consumption.

MVKE Sales data for material.

PKPF document header Reservation

TO23 Material Groups .

TO24 Purchasing groups .

T156 Movement Type

Purchasing Tables

EBAN Purchasing requisition.

EBKN Purchase requisition account assignment.

EKBE History per purchasing document.

EKET Scheduling agreement schedule lines.

EKKN Account assignment in purchasing document.

EKKO Purchasing document header.

EKPO Purchasing document Item.

IKPF Header Physical inventory document.

ISEG Physical inventory document items.

LFA1 Vendor master general data.

LFB1 Vendor Master (company Code)

RESB Reservation/Dependent requirement

MARD Storage location data for material.

( Important Fields)

MATNR Material Number (18C CT-MARA).

WERKS Plant (4C CT-MARC)

LGORT Storage location (4C)

LABST Valuated stock with unrestricted use (13 QUAN).

VMLHE Stock in transfer (from one storage location 2

another) (13 QUAN).

VNSHE Stock in quality inspection (13 QUAN)

MSEG Document segment material

(Important Fields)

MBLNR Number of matrial document (10C)

MJAHR Material document year.

ZEILE Item in material document.

MATNR Material number (18C CT-MARA).

WERKS Plant (4C CT-T001W).

KDPOS Item number is sales order(6C).

KDEIN Delivery schedule for sales order.

BUKRS Company code.

T001W Plant /Branches.

(Important Fields)

WERKS Plant

ANME1 NAme (30C).

EKORG Purchase organization (4C CT-T024E).

VSTEL Shipping /Rekieving port (4C).

EKKO Purchasing document header

( Important Fields)

EBELN Purchasing document number.

BUKRS Company code.

BSTYP Purchasing document category (1C).

BSART Purchasing document type (4C).

EKORG Purchasing organiation (4C CT-T024E).

EKGRP Purchasing group (3C CT-T024).

ANGNR Quotation number.

LLIEF Supplying Vendor (10C CT-LFA1).

KUNNR Customer number (10C CT-KNA1).

MEMORY Purchase Order not yet complete(1C).

T001L Storage Locations

(Important Fields)

WERKS Plant .

LGORT Storage location (4C) .

VSTEL Shipping /Recieving point (CT-TVST) .

VKORG SAles Organization (CT-TVKO).

VTWEG Distribution channel (CT-TVTW).

SPART Division (CT-TSPA).

MARC : Plant Data for material.

(Important Fields)

MANDT Client

MATNR Material Number

WERKS Plant

DISPR Material MRP Profile (4C).

DISMM MRP TYpe (2C) .

DISPO MRP Controller (3C).

PRCTR Profit center (10C).

TRAME Stock in transit (QUAN-13).

STLAN BOM Usage (1C).

What is a Stochastic Block?

2010-02-09T12:50:00.001-08:00

Written by Ada

You can block invoices at random to check them again. If the stochastic block is active and you post an invoice that is not subject to any other blocking reason, it can be randomly selected for blocking.
A stochastic block is not set at item level, but for the whole invoice. If a stochastic block is set when you post the invoice, the system automatically sets an R in the field Payment block in the document header data; there is no blocking indicator in the individual items.
In Customizing for Invoice Verification, you can define:
==If stochastic blocking is active==
The degree of probability of a block. You set a threshold value and a percentage for this.
- If the value of the invoice is larger than or the same as the threshold value, the degree of probability that the invoice will be blocked is that of the percentage.
- If the value of the invoice is smaller than the threshold value, the degree of probability that the invoice will be blocked is calculated proportionally to the percentage.
If, for example, the threshold value is $100 and the percentage 50%, every invoice over $100 would have a 50% chance of being blocked; an invoice for $500 would have a 25% change of being blocked. If you want the degree of probability to be the same for all invoices, you set the threshold value to zero.
If you enter a threshold value of zero and a percentage of 99.9%, all invoices would then be blocked

How to implement BADI to change a Purchase Order - Post-processing to ME21N

2010-02-09T12:44:00.001-08:00

How to implement BADI to change a Purchase Order - Post-processing to ME21N

Written by PAS

Requirement:

Populate EVERS [ Shipping Point ] at the time of purchase order creation. Shipping point should be derived from the shipping point on sales order [ if PO created from in reference to a sales order ].

Processing:

This is an example to show - how to achieve post-processing [ follow-on processing ] functionality using BADIs [ Business Add-inn ] or user-exits.

Find the relevant BADI using transaction SE18. In this case BADI ME_PURCHDOC_POSTED is used.
Further, implement the BADI using transaction SE19.
In Attributes section of BADI, define a STATIC attribute as PO_NUMBER. Static means the attribute will keep its value between the calls. This will be checked to ensure that same PO will not be processed twice. Also these kind of user-exits and BADIs might get called recursively and get caught into an infinite loop, if not coded properly. Remember that this BADI is at the time of PO save and then you are again trying to change & save the Purchase Order from within the BADI.
BAPI to change Purchase Order 'BAPI_PO_CHANGE' will be called IN BACKGROUND TASK to ensure that it will be called when COMMIT WORK is encountered.
Don't forget to activate the BADI implementation in SE19.

Sample ABAP Code:

method IF_EX_ME_PURCHDOC_POSTED~POSTED .
DATA: wa_ekpo like line of IM_EKPO,
      lt_po_item type standard table of BAPIMEPOITEM,
      lt_po_itemx type standard table of BAPIMEPOITEMX,
      wa_po_item type BAPIMEPOITEM,
      wa_po_itemx type BAPIMEPOITEMX,
      lt_return type standard table of BAPIRET2.
*data: ls_ebeln type BAPIMEPOHEADER-PO_NUMBER.
check im_ekko-ebeln ne PO_NUMBER.
PO_NUMBER = im_ekko-ebeln.
LOOP AT IM_EKPO into wa_ekpo.
wa_po_item-PO_ITEM = wa_ekpo-ebelp.
* EVERS to be derived
wa_po_item-SHIPPING = 'C'.
APPEND wa_po_item to lt_po_item .
wa_po_itemx-PO_ITEM = wa_ekpo-ebelp.
wa_po_itemx-SHIPPING = 'X'.
APPEND wa_po_itemx to lt_po_itemx.
ENDLOOP.
CALL FUNCTION 'BAPI_PO_CHANGE' IN BACKGROUND TASK
   EXPORTING
     purchaseorder                = PO_NUMBER
    NO_MESSAGING                 = 'X'
    NO_MESSAGE_REQ               = 'X'
    NO_AUTHORITY                 = 'X'
    NO_PRICE_FROM_PO             = 'X'
   TABLES
     RETURN                       = lt_return
     POITEM                       = lt_po_item
     POITEMX                      = lt_po_itemx.
endmethod.

EDI Functional Design

2010-02-09T12:34:00.001-08:00

EDI

Functional Design

table of contents

1 EDI Technical architecture..................................................................................................................... 3

1.1 Purpose................................................................................................................................................................... 3

1.2 EDI Interface Architecture......................................................................................................................... 3

1.3 Business Requirements................................................................................................................................... 3

1.4 Assumptions......................................................................................................................................................... 3

1.5 Functional Technical Design...................................................................................................................... 4

1.5.1 Outbound Message....................................................................................................................................... 4

1.5.2 Inbound Message.......................................................................................................................................... 5

1.6 Technical Design............................................................................................................................................... 6

1.6.1 Transfer Function......................................................................................................................................... 6

1.6.2 SAP Unattended Scheduler Function....................................................................................................... 6

1.7 External Dependencies.................................................................................................................................. 7

1 EDI Technical architecture

1.1 Purpose

The purpose of the document is to describe the functional technical design and the physical technical design of the EDI architecture. The secondary purpose of this document is to get approval to proceed with the detailed technical design and implementation of the EDI architecture.

1.2 EDI Interface Architecture

The purpose of the EDI interface architecture is to facilitate the movement and control of IDOC messages to and from the EDI sub-system. The EDI interface architecture will provide the basic components needed to automate the transfer of EDI messages between SAP and the EDI sub-system..

1.3 Business Requirements

· A mechanism to transfer EDI messages between the SAP system (UNIX) and the EDI sub-system (PC);

· The interface architecture should meet the short to medium term EDI requirements. These include:

Þ Low volume EDI traffic; and

Þ A cost effective solution resulting in basic control mechanisms.

· All standard operations procedures must be in place to operate the architecture. These procedures include:

Þ Installation;

Þ Start-up and shut-down; and

Þ Scheduler monitoring and maintenance.

1.4 Assumptions

· There will be a separate EDI sub-system for each SAP database server;

· An asynchronous batch driven interface (not event driven) with minimal controls will be developed to meet the short to medium term business requirements;

· Telkom will provide the translation mappings from an IDOC to an EDIFACT message and vice-versa;

· Telkom will provide all scripts for the Gentran:Director product i.e. translation maps, and upload and download scripts;

· All inbound IDOCs are appended to a single file per day; and

· All operational issues relating directly to the Gentran:Director product will be dealt with by the EC team.

1.5 Functional Technical Design

The functional technical design depicts at a technical level the functions offered by the proposed architecture. A functional technical design is provided for both outbound and inbound messages.

1.5.1 Outbound Message

Description

1. An EDI IDOC is created (in SAP) and stored in the sender queue at the UNIX operating system (OS) level;

2. A transfer process is activated that transfers the EDI IDOC from the sender queue to the EDI sub-system receiving queue;

3. The EDI sub-system control mechanism triggers (based on a schedule) the EDI translator which retrieves the IDOC file and translates the IDOCs into an EDIFACT standard message; and

4. The EDI sub-system transmits the EDIFACT message via the VAN.

Architectural Constraints

· Status information is not passed back to the SAP system to indicate a successful transmission of an EDI message. This would lead to manual controls, comparing EDI sub-system and SAP EDI system statuses; and

· The EDI sub-system cannot be externally triggered by SAP to initiate the outbound processes i.e. interface is not event driven.

1.5.2 Inbound Message

Description

1. A EDIFACT message is transported via the VAN and stored in the EDI sub-system;

2. The EDI control mechanism triggers off the translation process which translates the EDIFACT message into a IDOC message;

3. The EDI translator script stores the SAP IDOC in the sender queue;

4. A transfer process is activated that transfers the EDI IDOC from the sender queue to the EDI sub-system receiver queue; and

5. The SAP control mechanism triggers (based on a schedule) the SAP EDI inbound process which retrieves and imports the IDOC into the SAP system.

Architectural Constraints

· Status information is not passed back to the EDI sub-system to indicate a successful import of a EDI message into SAP.

1.6 Technical Design

1.6.1 Transfer Function

Only the custom components of the design are described below. The assumption is that the other components will be provided by the vendor and/or Telkom.

Requirements

· A transfer process which facilitates the movement of the IDOC from the UNIX directory to the PC directory and vice versa; and

· A basic error handling function.

Inputs

· IDOC message in Sender Queue.

Outputs

· IDOC message in Receiving Queue.

Mechanism

· NFS mounted drive;

· NFS exported drive - UNIX; and

· LAN Workplace PRO NFS client - PC.

Detailed Description

A directory will be exported as a NFS drive from the SAP UNIX box. This NFS drive will then be mounted on the PC via LAN Workplace PRO NFS client. A USER ID and PASSWORD will be required to mount the drive for security. The IDOC will be stored on the drive and will be “seen” by both the UNIX and PC Operating Systems as a standard file.

Technical Risks

· There is no transport validations beyond what the NFS mechanism provides; and

· There are security considerations to be considered with the use of NFS drives (i.e. well documented security holes within the NFS mechanism).

1.6.2 SAP Unattended Scheduler Function

Requirements

· A Control Module that triggers the SAP EDI inbound processes, which processes any IDOC messages which have been transferred to the SAP system directory.

Inputs

· Schedule.

Outputs

· Initiation trigger to the SAP EDI inbound process.

Mechanism

· SAP Job scheduler.

Detailed Description

A job will be inserted into the SAP job scheduler (SM36) which will initiate program “RSEINB00” (Inbound Processing of Intermediate Documents (EDI)) based upon a pre-determined schedule.

Technical Risks

· The EDI sub-system will receive no feedback from the SAP system on the status of the IDOC processing; and

· No automatic restart capabilities and error notification will be provided if the IDOC processing fails on the SAP box beyond the standard workflow provided by SAP.

1.7 External Dependencies

The following table identifies the key tasks/deliverables of external parties to the project:

Deliverable	Responsibility
Outbound Script (Gentran)
Inbound Script (Gentran)
Configuration of Gentran unattended scheduler (Outbound)
Configuration of Gentran unattended scheduler (Inbound)
Gentran Translation Mappings (IDOC to EDIFACT and vice-versa)

Workflow Email Forward

2010-02-09T07:31:00.001-08:00

RSWUWFML Report that interrogates the Workflow inbox, based on certain selections, and then forwards a notification to the respective users that they have email waiting in the SAP system. The auto-forwarding assignment of an email address to a user can be accomplished by the administrator and tx: SO36 or by the user themselves using tx: SO13. Use tx: SOST to view email status� sent from SAP.

Short text
Send Mails for Work Items

Title
Mail notification when new work items in Business Workplace

Purpose
The report sends notifications about work items to mail recipients by mail. Mails are only sent to those users for whom automatic forwarding has been set up. The send destination is the address maintained for automatic forwarding.

"Normally" (meaning not in an individual run) notifications are only created for work items that:

Have status ready or waiting
Were created since the last run (the time of the last run is stored in a table)
Have a recipient for whom automatic forwarding is set up
Purpose:
Users who do not use the Business Workplace of a particular SAP System as standard (other mail client, other SAP System) are notified in a simple manner
Workflow templates or workflow tasks do not have to be modified
Saves on consultant development time spent on setting up notification by mail (standard report)
Improves overall performance
The runtime of the report is less than several logons to the SAP System,which frequently have the result "no new work items ".
Prerequisites
Automatic forwarding must be configured for the recipients in question.

Features
Instance data:
Job suffix:
This means that several instances of the report can be run together. The other report parameters can be configured differently. The times of the last run are saved for the individual instances.
Tasks:
The selection of the work items can be restricted to work items for particular tasks (report parameters).
Send granularity:
One message per work item:
One mail is sent per new work item.
Only form work items:
Mails are only sent for work items that refer to a SAPforms form task.
Collective message:
Only one mail is sent for all the new work items of one user.
Type of mail:
With executable attachment:
The mails for work items that refer to a SAPforms form task are given an R3F attachment, others are not.
Without executable attachment:
No mails are given attachments.
Standard text for notification
You can configure the text of the mail by specifying a "dialog text".

Data for an individual run:
An individual run is when a date, a time and (optionally) a user are entered in the input fields. In an individual run (unlike a periodically scheduled run), the time of the last run is not saved.

From work item creation date:
The creation date of the work items for which messages are to be sent is not before this date.
From work item creation time:
The creation time of the work items for which messages are to be sent and which were created on the day From work item creation date is not before this time.
User (empty = all):
Notifications are only created for work items that this user has in their Business Workplace.
Log:
The report creates a log in a spool file when it is run. You can specify what is logged:

Nothing (indicator Nothing set)
Only error messages (indicator Only errors set)
Both success and error messages (indicator All set)
Properties:
If one mail is sent per work item, the mail contains the task description and the standard text for notification. If only one mail is sent for all work items, the mail contains only the standard text for notification. For express work items, express mails are sent.
One mail is sent to n recipients except for with SAPforms messages where one message is sent per recipient since the R3F attachment contains the recipient's mail. The message is sent to the user and then forwarded according to the automatic forwarding set up. Only SAPforms messages are sent directly to the automatic forwarding address. The e-mail is not kept in the "hidden folder" of the workflow_local user. It is therefore deleted automatically after the outbox expiry time.
The results of database queries (for example, addresses for automatic forwarding) are buffered for better performance.
Particular to SAPforms: If SAPforms messages are sent with R3F attachments, recipients of SAPforms work items should store an Internet address for automatic forwarding in their Business Workplace.
Selection
Determine the relevant work items.
Determine the recipients for each work item determined.
Only consider those recipients who have set up automatic forwarding.
If only one mail is sent for all work items, a check is made as to whether a mail has already been sent to this recipient.
Creation of mail transmission text (partly work item-specific).
Send mails to all recipients.
If work items refer to a form task and the mails are to be sent with executable attachment, a message is sent for each recipient.
Standard Variants
Variants can be defined for scheduling. If you use several, at least the job suffixes should be different.

Output
You can have the system create a log file.