Tuesday, 25 February 2025
Saturday, 29 May 2010
Tuesday, 20 April 2010
Note 753622 - Sending of body text and PDF attachment with medium 5
Tuesday, 30 March 2010
A Single Mistake Can Cost You $$$$$
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
Sunday, 28 March 2010
Monday, 22 February 2010
ONE TIME VENDOR
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
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.
System Task: Create a One-Time Vendor Master Record
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:Menu Path
From the SAP R/3 Screen, select the path:Logistics >> Materials management >> Purchasing >>(new menu) Master data >> Vendor >> Central >> CreateFast Path
At the Command Line, enter:/NXK01Create 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:
- 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.
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.
- Language
- Enter E for English.
Next Step...
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.
- Minority indic.
- Enter the code indicating whether the vendor is a small or minority-owned business.
- Prev. acct no.
- Enter the vendor's previous VAPS number if known.
Next Step...
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.
- 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.
Next Steps...
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.
- 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.
Saturday, 6 February 2010
BAPI PO Creation: Example & Documentation
FU BAPI_PO_CREATE1
____________________________________________________
Short Text
Create Purchase Order
Functionality
Function module BAPI_PO_CREATE1 enables you to create purchase orders. The BAPI uses the technology behind the Enjoy purchase order transaction ( ME21N).
Alternatively, the IDoc type PORDCR1 is available. The data from this IDoc automatically populates the interface parameters of the function module BAPI_PO_CREATE1.
Functionality in Detail
Authorization
The following authorization objects are checked when an Enjoy purchase order is created (activity 01):
M_BEST_BSA (document type in PO)
M_BEST_EKG (purchasing group in PO)
M_BEST_EKO (purchasing organization in PO)
M_BEST_WRK (plant in PO)
Controlling adoption of field values via X parameter
For most tables, you can determine via your own parameters in the associated X parameter in each case (e.g. PoItemX) whether fields are to be set initial, values inserted via the interface, or default values adopted (e.g. from Customizing or master records) (for example, it is not mandatory to adopt the material group from an underlying purchase requisition - you can change it with the BAPI).
Transfer
Header data
The header data of the Enjoy purchase order is transferred in the table PoHeader.
Item data
The item data of the Enjoy purchase order is stored in the table PoItem (general item data). The delivery schedule lines are stored in the table PoSchedule.
Use the table PoAccount to specify the account assignment information. If account assignments have been specified for services and limits, you show the relevant account assignment line in PoAccount in the table PoSrvAccessValues via the package number of the service or the limit.
Services and limits
Services, free limits and limits with contract reference can be specified in the tables PoServices, PoLimits, and PoContractLimits.
Conditions
Conditions are transferred in the table PoCond; header conditions in the table PoCondHeader. Price determination is reinitiated via the parameter CALCTYPE in the table PoItem.
Vendor and delivery address
The vendor's address can be specified individually in the table PoAddrVendor; the delivery address in the table PoAddrDelivery. If you do not make any individual specification, the fields will be populated via the central address management facility.
Note
In this method, the following restrictions apply with regard to addresses:
Addresses can only be created with this method - they cannot be changed. You can only change address data with the method BAPI_ADDRESSORG_CHANGE.
When you create addresses, they are not checked by the method. An Enjoy purchase order may therefore contain faulty address data.
Partner roles
The partners can be maintained individually via the table PoPartner (with the exception of the partner role "vendor").
Import/export data
Import/Export data can be specified per item in the table PoExpImpItem. Foreign trade data can only be transferred as default data for new items.
Texts
Header and item texts can be transferred in the tables PoTextHeader and PoTextItem. Texts for services are imported in the table PoServicesText.
Version Management
You can make use of the Version Management facility via the table AllVersions.
Return
The PO number is returned in the parameter ExpPurchaseOrder. In addition, all information except the service and export/import tables is placed in the output structures.
Return messages
Messages are returned in the parameter Return. This also contains information as to whether interface data has been wrongly or probably wrongly (heuristical interface check) populated. When a PO has been created successfully, the PO number is also placed in the return table with the appropriate message.
Restrictions
With this function module, it is not possible to:
Create subcontracting components (you can only use existing ones)
Create configurations (you can only use existing ones)
Change message records (table NAST) and additional message data (this data can only be determined via the message determination facility (Customizing))
Attach documents to the purchase order
See also further information in SAP Note 197958.
Example
Example of population of BAPI interface in the Function Builder
Parameter: POHEADER
COMP_CODE = 1000
DOC_TYPE = NB
ITEM_INTVL = 00001
VENDOR = 0000001000
PMNTTRMS = 0001
PURCH_ORG = 1000
PUR_GROUP = 001
CURRENCY = EUR
Parameter: POHEADERX
COMP_CODE = X
DOC_TYPE = X
ITEM_INTVL = X
VENDOR = X
PMNTTRMS = X
PURCH_ORG = X
PUR_GROUP = X
Parameter: POITEM
PO_ITEM = 00001
MATERIAL = 100-100
PLANT = 1000
STGE_LOC = 0001
QUANTITY = 15.000
TAX_CODE = V0
ITEM_CAT = 0
ACCTASSCAT = K
Parameter: POITEMX
PO_ITEM = 00001
MATERIAL = X
PLANT = X
STGE_LOC = X
QUANTITY = X
TAX_CODE = X
ITEM_CAT = X
ACCTASSCAT = X
Parameter: POSCHEDULE
PO_ITEM = 00001
SCHED_LINE = 0001
DELIVERY_DATE = 02.12.2002
QUANTITY = 6.000
PO_ITEM = 00001
SCHED_LINE = 0002
DELIVERY_DATE = 03.12.2002
QUANTITY = 5.000
PO_ITEM = 00001
SCHED_LINE = 0003
DELIVERY_DATE = 04.12.2002
QUANTITY = 4.000
Parameter: POSCHEDULEX
PO_ITEM = 00001
SCHED_LINE = 0001
PO_ITEMX = X
SCHED_LINEX = X
DELIVERY_DATE = X
QUANTITY = X
PO_ITEM = 00001
SCHED_LINE = 0002
PO_ITEMX = X
SCHED_LINEX = X
DELIVERY_DATE = X
QUANTITY = X
PO_ITEM = 00001
SCHED_LINE = 0003
PO_ITEMX = X
SCHED_LINEX = X
DELIVERY_DATE = X
QUANTITY = X
Parameter: POACCOUNT
PO_ITEM = 00001
SERIAL_NO = 01
QUANTITY = 15.000
GL_ACCOUNT = 0000400000
COSTCENTER = 0000001000
CO_AREA = 1000
Parameter: POACCOUNTX
PO_ITEM = 00001
SERIAL_NO = 01
QUANTITY = X
GL_ACCOUNT = X
COSTCENTER = X
CO_AREA = X
Parameter: POCOND
ITM_NUMBER = 000001
COND_ST_NO = 001
COND_TYPE = PB00
COND_VALUE = 79.900000000
CURRENCY = EUR
CURRENCY_ISO = EUR
COND_UNIT = KG
COND_P_UNT = 1
CHANGE_ID = U
Parameter: POCONDX
ITM_NUMBER = 000001
COND_ST_NO = 000
ITM_NUMBERX = X
COND_TYPE = X
COND_VALUE = X
CURRENCY = X
CHANGE_ID = X
Parameter: POPARTNER
PARTNERDESC = OA
LANGU = EN
BUSPARTNO = 0000001100
PARTNERDESC = GS
LANGU = EN
BUSPARTNO = 0000001200
PARTNERDESC = PI
LANGU = EN
BUSPARTNO = 0000001000
Help in the Case of Problems
SAP Note 197958 lists answers to frequently asked questions (FAQs). (Note 499626 contains answers to FAQs relating specifically to External Services Management.)
If you have detected an error in the function of a BAPI, create a reproducible example in the test data directory in the Function Builder (transaction code SE37). SAP Note 375886 tells you how to do this.
If the problem persists, create a Customer Problem Message for the componente MM-PUR-PO-BAPI, and document the reproducible example where appropriate.
Customer Enhancements
The following customer exits (function modules) are available for the BAPI BAPI_PO_CREATE1:
EXIT_SAPL2012_001 (at start of BAPI)
EXIT_SAPL2012_003 (at end of BAPI)
The following customer exits (function modules) are available for the BAPI BAPI_PO_CHANGE:
EXIT_SAPL2012_002 (at start of BAPI)
EXIT_SAPL2012_004 (at end of BAPI)
These exits belong to the enhancement SAPL2012 (see also transaction codes SMOD and CMOD).
There is also the option of populating customers' own fields for header, item, or account assignment data via the parameter EXTENSIONIN.
Further information
Further information on purchase order BAPIs is available in SAP Note 197958.
If you test the BAPIs BAPI_PO_CREATE1 or BAPI_PO_CHANGE in the Function Builder (transaction code SE37), no database updates will be carried out. If you need this function, take a look at Note 420646.
The BAPI BAPI_PO_GETDETAIL serves to read the details of a purchase order. The BAPI cannot read all details (e.g. conditions). However, you can use the BAPI BAPI_PO_CHANGE for this purpose if just the document number is populated and the invoker has change authorizations for purchase orders.
Frequently used BAPIs for purchase orders are BAPI_PO_CREATE, BAPI_PO_CREATE1, BAPI_PO_CHANGE, BAPI_PO_GETDETAIL, BAPI_PO_GETITEMS, BAPI_PO_GETITEMSREL, and BAPI_PO_GETRELINFO.
For more information on purchase orders, refer to the SAP library (under MM Purchasing -> Purchase Orders) or the Help for the Enjoy Purchase Order, or choose the path Tools -> ABAP Workbench -> Overview -> BAPI Explorer from the SAP Easy Access menu.
Parameters
POHEADER
POHEADERX
POADDRVENDOR
TESTRUN
MEMORY_UNCOMPLETE
MEMORY_COMPLETE
POEXPIMPHEADER
POEXPIMPHEADERX
VERSIONS
NO_MESSAGING
NO_MESSAGE_REQ
NO_AUTHORITY
NO_PRICE_FROM_PO
EXPPURCHASEORDER
EXPHEADER
EXPPOEXPIMPHEADER
RETURN
POITEM
POITEMX
POADDRDELIVERY
POSCHEDULE
POSCHEDULEX
POACCOUNT
POACCOUNTPROFITSEGMENT
POACCOUNTX
POCONDHEADER
POCONDHEADERX
POCOND
POCONDX
POLIMITS
POCONTRACTLIMITS
POSERVICES
POSRVACCESSVALUES
POSERVICESTEXT
EXTENSIONIN
EXTENSIONOUT
POEXPIMPITEM
POEXPIMPITEMX
POTEXTHEADER
POTEXTITEM
ALLVERSIONS
POPARTNER
POCOMPONENTS
POCOMPONENTSX
POSHIPPING
POSHIPPINGX
POSHIPPINGEXP
Exceptions
Function Group
2012
Wednesday, 27 January 2010
Purchasing Tables = Vendor
| Segment | Description |
| SKA1 | G/L master (chart of accounts area) |
| SKAT | G/L account master (chart of accts. area: description) |
| SKB1 | G/L account master (company code master) |
| SKAS | G/L account master (chart of accounts: key word directory) |
The FI_ACCRECV archiving object consists of the following segments:
| Segment | Description |
| KNA1 | Customer master (general part) |
| KNBK | Customer master (bank details) |
| KNAS | Customer master (VAT registration number general section) |
| KNAT | Customer master (tax groups) |
| KNKA | Customer master credit management: central data |
| KNKK | Customer master credit management: control area |
| KLPA | Customer/vendor linking |
| KNZA | Permitted alternative payer |
| KNB1 | Customer master (company code) |
| KNB5 | Customer master (dunning data) |
| KNB4 | Customer payment history |
| KNVA | Customer master loading points |
| KNEX | Customer master: export control file |
| KNVI | Customer master tax indicator |
| KNVL | Customer master licenses |
| KNVK | Customer master contact partner |
| KNVS | Customer master shipping data |
| KNVV | Customer master sales data |
| KNVD | Customer master record sales request form |
| KNVP | Customer master partner functions |
| KNMT | Customer material info record data table |
The FI_ACCPAYB archiving object consists of the following segments:
| Segment | Description |
| LFA1 | Vendor master (general section) |
| LFB1 | Vendor master (company code) |
| LFB5 | Vendor master (dunning data) |
| LFAS | Vendor master (Vat registration number general section) |
| LFAT | Vendor master (tax groups) |
| KLPA | Customer/vendor linking |
| LFBK | Vendor master (bank details) |
| LFZA | Permitted alternative payees |
| LFM1 | Vendor master (purchasing organization) |
| WYT1 | Vendor sub-range |
| WYT1T | Vendor sub-range: description |
| LFLR | Vendor master record: supply regions |
| LFM2 | Vendor master record: purchasing data |
| WYT3 | Partner functions |
| EINA | Purchasing information record - general data |
| EINE | Purchasing information record (purchasing organization data) |
| LFEI | Vendor master - preference for import and export |
| KNVK | Vendor master - contact person |
Friday, 22 January 2010
Upload Text file to Header or Item Text in Purchase Order
Right click on header text. There you see load local file. Click on that, select txt file location and load it.
OR
Right click on header text. There you see load local file. Click on that, select txt file location and load it.
http://help.sap.com/saphelp_sm32/helpdata/en/d6/0db7f3494511d182b70000e829fbfe/content.htm
Saturday, 19 December 2009
Sunday, 6 December 2009
REQUIREMENTS FOR CONDITIONS
-
Converting External Customer Number To Internal Customer Number – SAP EDPAR Table Have you ever had a project where you are converting a c...
-
FU BAPI_PO_CREATE1 ____________________________________________________ Short Text Create Purchase Order Functionality Function ...
-
How to implement BADI to change a Purchase Order - Post-processing to ME21N Written by PAS Requirement: Populate EVERS [ Shipping Poin...
