Transporter payment
Hello,
The scenario is sometimes payment is to be made on proforma invoice issued by supplier, against letter of credit.
how it will happen in sap.
urgent
Hi,
I think it can be handled by means of the downpayments(Special GL transactions).
Correct me if Iam wrong.
Aravind.
Assign points if helpful
Similar Messages
-
Hi,
I wanna restrict the double payment to transporter against the same sales Invoice/Delivery.
Please suggest.
Regards
Ankur
Edited by: Ankur Gupta on Jun 6, 2011 11:08 AMPlease search the forum with the text TRANSPORTATION so that you will get many threads. Take the input from there, try on your own and still if you face any issue, please post it.
Being an old member, I dont want to stress on the importance of putting efforts to search the forum which you should be aware of.
thanks
G. Lakshmipathi -
Hello,
we are implementing SRM 4.0 in standalone scenario.
We would like to know how payment terms could be transpored from a dev system to a validation system and to a production system.
Indeed, payment terms which are created through SPRO dedicated transaction are put into a transport request with the logical system related to the dev system. Therefore, after transport to val, the logical system is not correct ...
We have noticed that the tables BBP_PAYTERM and BBP_PAYTERM_TEXT which handle the payment terms could be maintained directly through SE16.
We then thought to maintain all our records directly into dev system with SE16 for logical systems val & pro and to put them manually into a transport request.
Do you know a better solution ?
Thank you for your help.
Regards.
FabriceHi Fabrice,
Payment terms can be replicated from backends with report BBP_UPLOAD_PAYMENT_TERMS (in that case they have the backend Logical System as key) or maintained locally (in that case the LS is the local one).
For backend values, you can replicate them between each val/val, prod/prod server.
But for local ones, you are right, the source LS is transported with the values. So we have to adapt the LS of those tables in the target system.
You should run transaction BDLS, limited on this table, to adapt the LS.
Rgds
Christophe
PS: please reward points for helpful answers -
Hi all,
FB60 :- Instant deductions from Transporter's payment because of leakage/damage/Pilferage(w/o debit memo), please explain me how to configure this scenario.hi,
Transporter's payment
You are define tds condition transporter payment,so automatic system deduct the tds. and you are pass the entry.
tds rate define.
Select Firm ( OT)
rohit -
Vendor payment terms replication
Hi,
Vendor payment terms are not getting replicated to SRM 4.0 from ECC 5.0.We have batch jobs running for vendor replication ( new and update).When i change the payment terms in ECC , it is not coming to SRM.I checked in Manage BPs.
Thanks for suggesting any report / tables where i can find number of vendors that are different in both the systems and replication process. ( As i am unable to use the t code BBPGETVD, BBPUPDVD in easyaccess)
Thanks a lot.Hi pramod,
OK. I got it.
SAP Note 1104581 -No logical system in customizing view
BBPV_PTERM_LOCAL
Symptom
You have transported local payment term Customizing (view BBPV_PTERM_LOCAL)
from your SRM development system to a productive system.
The transported payment terms cannot be selected for local purchase orders
and are not visible in Customizing step "Supplier Relationship Management >
SRM Server > Cross-Application Basic Settings > Create Payment Conditions".
More TermsZTERM, pay, BBP_POC, payment tab, terms of payment
Cause and Prerequisites
Local payment terms must have the local logical system ID in the
corresponding fields of tables BBP_PAYTERM and BBP_PAYTERM_TEXT.
Solution
Please implement this note or the relevant Support Package.
You can then use report BBPCU_PAYTERM_CONV to change the logical system of
the transported entries to the local SRM logical system.
In the single selection parameter, enter the logical system of the
transported entries.
An error will be generated if the entered logical system exists in table
BBP_BACKEND_DEST.
If an entry already exists with the same key (apart from logical system
name) as the tranported entry, no conversion will take place.
The keys of the converted payment terms and their texts will be listed
after executing the program.
The keys of the payment terms that cannot be converted will also be lsited.
table BBP_PAYTERM or BBP_PAYTERM_TEXT.
BBPM_BUT_FRG0061
Payment conditions
i will also check and come back to you.
regards
muthu -
To capture Trip details during MIGO
Dear SAP Team,
I have two scenerios being in practise by my client Request that if any one can give me the solution
1. When the material supplier is not taking care of the transport ,at the time of good receipt there is one activity called "TRIP DETAILS" done by my client during GR. Details is maintaied in the "Trip details "for transporter payment like transporter name ,vehicle no, gate pass no,material, Transport Order no with the transporter .They also want during this activity the trip detail tab page must be made mandatory so that the user does not omit the relevant transporter data
2.Vendor supplies materials to the Client in two ways - One where vendor take care of the freight cost which can be tracked in PO. In second case , they arranges the transport for whom the transport contract exists based on the distance.When the GR is made for this the product cost to be captured where there are two activities for the material.( One is material supplied by vendor / Transporter.The payment is done for the two sepately
Regards,
Suresh.RIn both the cases, freight will be there. So goto M/06 select your condition type-go to details- Control data 2- here maintain Vendor in GR - 2.
This is nothing but delivery cost, you can change the vendor code (either your transporter or main vendor) during GR.
As far as other transport details are concerned, you can make the field "header Text' mandatory & use it to maintain such details. -
For a po item there are two vendors one for goods supplier and other for delivery charges to local transporter. We have done payment to goods supplier using miro but payment to transport vendor is posted using FI transaction. How can we identify the list of miro s for which the status shows pending for transporter payments and how do we identify the payment made through fi are with reference to which po.
Hi
Run tcode MIRO for this PO with the option planned delivery cost instead goods/service items. If you have huge differences, then do 2 FI documents, one clearing the document from MIRO and the right amount with FB60.
I hope this helps you
Regards
Eduardo -
Dear Friends,
We have done a z development for LR entry(Lorry Receipt) for Primary and secondary Freight.
As soon as shipment completes user has to do the LR entry of concerned transporter per shipment wise.
LR no is a receipt from transporter against the material he is going to transport to customer or plant.
LR contains the invoice numbers/ gross value/date etc.
On the basis LR and proof of delivery(2nd copy of LR signed/stamped by receiver)payment made to transporter.
One LR no. may be of multiple deliveries/invoices.
Issue we are facing in case of primary freight(plant to plant transfer) where some supplying plant forgets to do the LR entry.
Again we had created a field LR no and date and made the field mandatory at the time of MIGO. In MIGO as soon as users enters the delivery no. its update the LR no from the Z table and if supplying plant has not done the LR entry , receiving plant has to do with the reference of hard copy.
Many time user does the wrong entry due to which transporter payment got delayed.
Can anyone give a better solution for this so that timely payment or deduction of payment can be managed.
Regards
Raviand made the field mandatory at the time of MIGO
Instead of making the field mandatory in receiving plant, as already suggested, have a control in such a way that sending plant should update the LR entry within 3 or 5 days (depending upon client's discretion), failing which, all out going transactions should be locked. Only top management should have the authorization to release this lock. On the other hand, if the transporter enjoys very good business with your client, then you can very well hand over this work to the transporter who has to update then and there when they release LR. This practice is being followed by many major clients. By doing so, your client can not only pass on the message that LR updation will have parallel impact on their payment, but also users job is simplified. They just need to validate the data which can be done by having some report with details like Transporter name, Vehicle no. (if required), date of despatch, Delivery reference etc.
G. Lakshmipathi -
could you make me familiar with the concept of THIRDPARTY without MIRO
thanks in advance
krishDear,
I can't understand your problem. But as per my knowladge you want to learn about third party concept.It is as bellow.
When you create purchase order for material, to transfert it from manufacture to your plant you have pay some amount to transporter. So at the time of this type of scnario two bill for payment.
1. For material payment
2. For transporter payment.
Now for both it is possible both vendor 1. who is provide you material and 2. who is provide you service for tranfer your material so mya be possible that both are different.
So at the time of this type of scnario we maintain second vendor at the item level of purchase order ---> condition type ---> Transporter Third party ---> header ---> Define vendor code.
So with help of this condition type - Transporter third party you can prepaid two invoice verification for two different vendor.
It it is useful for u, Please check and confirm.
Regards,
Mahesh Wagh -
Terms of payment - Transportation document
Dear All,
We are using payment terms in our business scenario. Our payment terms will follow customer received for calculation of discount.
We are using Transportation documents for shipping the deliveries. Each transportation document will applicable to only one customer. If the customer is having more than one delivery, we are clubbing the all the deliveries and creating the transportation document.
After confirmation of the customer, forwarding agent will give the confirmation based on the transportation document.
How can I give the receiving date of the customer, for calculating the terms of Payment terms for each invoice.
Plz help me out
Regards,
Ramakrishnahello, friend.
well, there are a few ways to meet your requirement. you can try any of the following:
1. the system can take your invoice date as baseline for calculating payment terms; therefore, enter the customer acknowledgement date as your billing date when creating and saving billing documents.
2. you can also go for Proof-of-Delivery, which is similar but a little more complicated because you have to activate this on several levels (customer, item category, schedule lines, etc.); what this means is that you can bill a delivery only when you receive the customer's acknowledgement of receipt of delivery. to process POD, you can use VLPOD or VLPODL (you can use for parameters, the outbound delivery, delivery group, shipment number, etc.).
regards. -
Payment voucher to be transporter
Hi..
I am preparing things for some taxtile Industry. My scenerio is as follows :
Whenever we get Gray to our General Warehouse from where we send it to client's Dying Factory. When we issue challan for it, we are supposed to gererate Payment Voucher for the Transporter.
How can I do it so that I can have track the payment made for each transaction for it. Actually , it would help to calculate expaneses done on particular dying.
Please help me in step by step manner.
Regards
Akritihi,
Assume ur doing stock transfer grey to dyeing subcontractor,
Payment voucher to transporter can be done using outgoing payment vendor/on account option,
Create a user defined fields in outgoing payment for
transporter name,
*stock transfer document number,*processing details etc.,
By this way u can track payment details transaction wise,
Create a query to calculate expenses.
Jeyakanthan
Edited by: Jeyakanthan A on Jun 19, 2009 2:36 PM
Edited by: Jeyakanthan A on Jun 19, 2009 2:37 PM -
No transport request generated while configure the payment terms
Hi Gurus,
When i am configure the payment terms in DEV with tcode OBB8,At that time the system is not generated any transport request,plz give the any other process for creation of transport request.
Regards,
RameshHi gpr rao,
From screen Txn OBB8>Table view>Transport>Create request. Now you will get the transport number.
Hope this will help.
TQ
Regards,
Nazrul -
Transporting changes made to Payment terms
Hi all,
Is the procedure to transport the changes made to payment terms in IMG, different from usual transports? because I was not asked for a request, when I changed the description of the payment term for customers in IMG.Please let me know the procedure.
Thanks in advance
KumarHi,
In the IMG, payment terms, , select the payment terms you want to transport, go to menu-- click on transport --then u will get include in request and delete from request, click on include in request, then u will get the request creation pop up, then create a new request, release and then transport the request.
Hope this helps.
Thanks,
Viswanath -
HELLO EXPERTS,
NOW I M PURCHASING MATERIAL FROM MY VENDOR.
HERE IN PARTNER FUCTION I M GIVING TRANSPORTER'S NAME.
I HAVR TO PAY MY VENDOR AND TRANSPORTER SEPARATELY.
HOW IT CAN POSSIBLE ??
SO THAT I THROUGH T.CODE MIRO I M ABLE TO PAY TO DIFFERENT VENDOR SEPARATELY.
KINDLY REPLY SOON.
REGARDS RAGHU.Hi
In condition type configuration (Use T.code M/06), choose cond.category as B-delivery cost for transport cost. then you can enter a seperate vendor in PO for that condition type in condition details.
In MIRO, if you choose option only Planned delivery cost then you will be able to pay transporter and then again do MIRO for Goods/services. You will be able to pay multiple vendor.
Hope you are clear.
Regards
Antony -
Tables for vendor invoice and payment
Hi Gurus.
I want to know from which tables i can get the information for folllowing points.
1. Vendor Invoices - Complete (Header and Item)
2. Vendor Payments Details Detail about payment method (check, wire, etc)
Please tell me tje table names.There is no specific table for header/item data for vendor invoice. Various information regarding vendor invoice (FB60) are stored in the following tables( note: Ignore the structures in the list ).
|Table Name |Table Description |
|/BEV3/CHKOMPAZVV |Append Structure CH -> CO PA |
|/CWM/ACCIT |Append Structure for Enhancement of Structure ACCIT in CWM |
|/CWM/KOMP |Catch Weight Management Enhancement |
|/DSD/TAXJURCD |Ship From Tax Jurisdiction Code: for Header Prc Comm Str |
|/SAPNEA/J_SC_LFA1 |Subcontractor Information |
|/SAPNEA/J_SC_LFB1 |Subcontracting Management |
|/SAPPSPRO/A_FI2_LONGNUM |IBU-PS: Append structure for structure NONBSEG |
|/SAPPSPRO/A_LONGNUMBER |additional fields for SPIIN number |
|/SAPPSPRO/EADD |Purchasing Document Header: Additional Data |
|/SAPPSPRO/EADD_DATA |Purchasing Document Header: Data Part Additional Information|
|/VSO/R_KNA1_A |Append to KNA1 for Vehicle Space Optimization |
|/VSO/R_KNA1_I |Additional Data for Vehicle Space Optimization for KNA1 |
|AACCHD_FMFG |US federal fields |
|AACCHD_PSO |IS-PS: ACCHD Append Structure for Payment Requests |
|AACCIT_GM |Append for Grants Management |
|AACCIT_PSO |IS-PS: ACCIT Append Structure for Payment Requests |
|AACCIT_SSP |Append for Payment Statistical Sampling Process |
|AACCIT_USFG |Append structure for US federal government |
|AAUSZ_CLR_USFG |Clearing information for US Fed (Tresury Confirmation) |
|ABKPF_PSO |IS-PS: BKPF Append Structure for Payment Requests |
|ABKPF_UMB |IS-PS: Append Structure for Transfer Transaction FMITPO |
|ABSID_PSO |IS-PS: Data appendix of open items customers |
|ABSIK_PSO |IS-PS: Data appendix of open items vendors |
|ABSIS_PSO |Local Authorities |
|ABUZ |Help Structure for Line Items to be Generated Automatically |
|ACCCR |Accounting Interface: Currency Information |
|ACCCR_FKEY |Key: Acctg Currency Data for Line Item Including Currency |
|ACCCR_KEY |Key: Accounting Currency Data for Line Item |
|ACCFI |Interface to Accounting: Financial Acctg One-Time Accts |
|ACCHD |Interface to Accounting: Header Information |
|ACCHD_KEY |Key: FI/CO Document Header |
|ACCIT |Accounting Interface: Item Information |
|ACCIT_EXTENSION |ACC Document: Additional Item Information |
|ACCIT_JV |Joint Venture Accounting |
|ACCIT_KEY |Key: FI/CO Line Item |
|ACCIT_WT |Withholding tax information for FI Interface |
|ACCRDF |Fields for Posting Small Differences: Preparation |
|ACC_DOCUMENT |Accounting document |
|ACC_KONTEXT |Context Info for FI Single Screen Transactions FB50 and FB60|
|ACERRLOG |Return Parameter |
|ACGL_HEAD |Fields for Document Header Entry Screen |
|ACGL_ITEM |Structure for Table Control: G/L Account Entry |
|ACSCR |Communication Structure for Field Modification SAPLFDCB |
|ACSPLT |Carrier for Split Information re: Current Account Line Items|
|ACSPLT_WTNEW |Proportion of New Withholding Tax |
|ACSPLT_WTOLD |Proportion of Old Withholding Tax |
|ADDR1_SEL |Address selection parameter |
|AEBPP_KNBK |Additional Fields Bank Data Biller Direct |
|AEBPP_LFBK |Additional Fields Bank Data Biller Direct |
|AFMIOI |Append for new fields ECC50/ERP |
|AFMIOI_USFG | SD order needs quantity |
|AFMISPS |Additional Fields for Table FMISPS |
|AFM_ACCIT_EXTENSION |Extension for FM Payment Update |
|AFM_FAGL_GLT0_ACCIT_EXT |Extension FM Account Assignments |
|AFM_FI_BKPF_SUBST |Append to Structure BKPF_SUBST |
|AFM_FMFCTF |Append for Fund Center substrings |
|AFM_FMFINCODE |Append for Fund substrings |
|AIFM01D |Append for IFM01D |
|AKNA1_FMFG |US Federal Government Customer Master Data Additional Fields|
|AKNA1_PSO |Local Authority Additional Fields |
|AKNB1_PSO |IS-PS: Customer Master Record, Additional Data (Co.Code) |
|AKNBK_PSO |Bank Details Dependent on Time and Account Holder |
|ALFA1_FMFG |US Federal Government Vendor Master Data Additional Fields |
|ALFA1_PSO |Local Authority Additional Fields (Address) |
|ALFB1_FMFG |PS fields for company code-specific master data field |
|ALFB1_PSO |IS-PS: Data Appendix Vendor Master Record (Company Code) |
|ALFBK_PSO |Bank Details Dependent on Time and Account Holder |
|ALVDYNP |ALV dialog screen fields |
|ALV_S_FCAT |Field Catalog (for LVC and for KKBLO) |
|ALV_S_FILT |Filter Criteria (for LVC and for KKBLO) |
|ALV_S_GRPL |Group Levels (for LVC and for KKBLO) |
|ALV_S_LAYO |Layout (for LVC and for KKBLO) |
|ALV_S_PCTL |Structure for Checking Print in ALV |
|ALV_S_PRNT |Print settings (for LVC and KKBLO) |
|ALV_S_QINF |Structure for Quickinfos of Exceptions |
|ALV_S_SGRP |Field Groups (for LVC and for KKBLO) |
|ALV_S_SORT |Sort Criteria (for LVC and for KKBLO) |
|ANBZ |Help structure for asset line item |
|ANLZACCOUNT |Additional Account Assignment Objects in Asset Accounting |
|ANLZACCOUNT_FKBER |Account Assignment Objects: ANLZACCOUNT with Function Added |
|ARC_PARAMS |ImageLink structure |
|AT003_XBLNR2 |Append structure for US federal government |
|AUSZ1 |Clearing Table 1 |
|AUSZ2 |Clearing Table 2 |
|AUSZ_CLR |Assign Clearing Item to Cleared Items |
|AUSZ_CLR_ASGMT |Assgt of Clrg Items - Cleared Items with Acct Assignment |
|AUSZ_INFO |Open item data for clearing transactions |
|AVBKPF_FMFG |US federal |
|AVBKPF_PSO |IS-PS: Append Structure VBKPF for Payment Requests |
|AVBSEGDPSO |IS-PS: Append Structure VBSEGD for Payment Requests |
|AVBSEGKPSO |IS-PS: Append Structure VBSEGK for Payment Requests |
|AVIK |Payment Advice Header |
|AVIP |Payment Advice Line Item |
|BALHDR |Application log: log header |
|BALMT |Application Log: Structure for a formatted message |
|BAL_S_CLBK |Application Log: Return routine definition |
|BAL_S_CONT |Application Log: Context |
|BAL_S_MSG |Application Log: Message Data |
|BAL_S_PAR |Application Log: Parameter Name and Value |
|BAL_S_PARM |Application log: Parameters |
|BAPIASCONT |Business Document Service: File Content ASCII |
|BAPIBDS01 |Business Document Service: Reference Structure for BAPIs |
|BAPICOMFIL |BDS: Command File for Transport Entries |
|BAPICOMPO2 |SBDS: Enhanced Component Information |
|BAPICOMPO3 |SBDS: Enhanced Component Information |
|BAPICOMPON |Business Document Service: Component Table |
|BAPICONNEC |BDS: Structure for BDS Links |
|BAPICONTEN |Business Document Service: File Content |
|BAPIDPROPT |BDS: Structure for Properties |
|BAPIFILES |Business Document Services: Transfer Table for File Names |
|BAPIPROPER |BDS: Structure for Properties |
|BAPIPROPTL |BDS: Structure for KPRO Properties |
|BAPIQUERY |BDS Structure for Query Table |
|BAPIRELAT |Business Document Service: Relations |
|BAPIRET1 |Return Parameter |
|BAPIRETURN |Return Parameter |
|BAPISIGNAT |Business Document Service: Signature Table |
|BAPISRELAT |Business Document Service: Relationship Table with Signature|
|BAPIURI |Business Document Service: URI Table |
|BDCMSGCOLL |Collecting messages in the SAP System |
|BDCRUN |Batch input: Runtime analysis |
|BDIDOCSTAT |ALE IDoc status (subset of all IDoc status fields) |
|BDI_SER |Serialization objects for one/several IDocs |
|BDN_FKT |Business Document Navigator: Functions to be Excluded |
|BDWFAP_PAR |Parameters for application function module - IDoc inbound |
|BDWFRETVAR |Assignment of IDoc or document no. to method parameter |
|BDWF_PARAM |Parameters for workflow methods for IDoc inbound processing |
|BKDF |Document Header Supplement for Recurring Entry |
|BKDF_SUBST |Process Interfaces: Substitutable fields during posting |
|BKORM |Accounting Correspondence Requests |
|BKP1 |Document Header Supplement for Update |
|BKPF |Accounting Document Header |
|BKPFBU_ALV |Document Overview: Display Document Headers in ALV Grid Ctrl|
|BKPF_CARD |Credit Card: Append for BKPF |
|BKPF_LINE |Item Category for XBKPF_TAB |
|BKPF_SUBST |Process Interfaces: Substitutable Fields During Posting |
|BKPF_USFED |Append structure for US federal government |
|BLNTAB |Document Number Table for Financial Accounting |
|BNKA |Bank master record |
|BNKAAPP |Appendix to Table BNKA |
|BNKT |Conversion of temporary to internal bank keys |
|BOOLE |Boolean variable |
|BSEC |One-Time Account Data Document Segment |
|BSEC_LINE |Item Category for XBSEC_TAB |
|BSED |Bill of Exchange Fields Document Segment |
|BSEE |Changeable Fields in the Line Item |
|BSEG |Accounting Document Segment |
|BSEGL |Document Segment: Fields Derived for Line Layout Variant |
|BSEGS |G/L Item Transfer Structure for Single Screen Transactions |
|BSEGT |Transfer Table for the Tax Postings to be Generated |
|BSEGZ |Financial Acctg Doc.Segment: Extras and Temp. Storage Fields|
|BSEG_ALV |Document Overview: Document Item Display in ALV Grid Control|
|BSEG_LINE |Item Category for XBSEG_TAB |
|BSEG_SUBST |Process Interfaces: Substitutable Fields During Posting |
|BSET |Tax Data Document Segment |
|BSEU |Line Item Additional Information (Update) |
|BSEZ |Line Item Additional Information (Online) |
|BSEZ_LINE |Line Item Category for XBSEZ_TAB |
|BSID |Accounting: Secondary Index for Customers |
|BSIK |Accounting: Secondary Index for Vendors |
|BSIP |Index for Vendor Validation of Double Documents |
|BSIS |Accounting: Secondary Index for G/L Accounts |
|BSIX |Index table for customer bills of exchange used |
|BTXKDF |Fields for Exch.Rate Difference Posting for Taxes |
|BVOR |Intercompany posting procedures |
|CACS_A_CRM_SALES_COND |Additional CRM Fields (Construction) From Sales Order Area |
|CACS_A_CUST_COND |Commissions: Customer Fields Condition Technique |
|CACS_A_FIELDSPRICING |Append for Condition Technique Fields from Commission System|
|CACS_S_CRM_SALES_COND |Additional CRM Fields (Construction) From Sales Order Area |
|CACS_S_CUST_COND |Condition Attributes |
|CACS_S_FIELDSPRICING |Comm.: All Condition Technique-Relevant Commission Fields |
|CACS_S_FSINS |Customer Fields for Condition Technique of Insurances |
|CCDATA |Payment cards: Database fields relevant to both SD and FI |
|CFW_LINK |CFW: Link Info of a Container |
|CI_COBL |Extension |
|CKI_ACCIT_ML |Transfer from MM to ML in accit-structure |
|CNTLSTRLIS |Control stream list |
|COBK |CO Object: Document Header |
|COBK_ONLY |Non-key fields only in COBK (INCLUDE structure) |
|COBL |Coding Block |
|COBLF |Coding block: Tax table structure |
|COBL_COKZ |Assignment types for CO account assignments |
|COBL_DB_INCLUDE |Include with Additional Account Assignments for DB Tables |
|COBL_EX |Coding Block for External Applications (Not CO/FI) |
|COBL_FI |Fields from COBL that Must not Be Overwritten in FI |
|COBL_FM |Additional Fields for FM |
|D010SINF |Generated Table for View D010SINF |
|D020S |System table D020S (screen sources) |
|D020T |Screen Short Description |
|DBSEG |Dialog Supplementation BSEG (Taxes) |
|DD02L |SAP Tables |
|DD03P |Structure |
|DD03V |Table fields view |
|DD07V |Generated Table for View DD07V |
|DD23L |Matchcode ID |
|DD32P |Interface structure for search help parameters |
|DDSHDEFLT |Description of a default value for search help fields |
|DDSHDESCR |Interface: elementary search helps of a search help |
|DDSHFPROP |Characteristics of search help parameters |
|DDSHIFACE |Interface description of a F4 help method |
|DDSHRETVAL |Interface Structure Search Help <-> Help System |
|DDSHSELOPT |Selection options for value selection with search help |
|DDSUX030L |Nametab Header, Database Structure DDNTT |
|DDSUX031L |Nametab Structure, Database Structure DDNTF |
|DDTYPES |Table of all Dictionary types and classes |
|DFIES |DD Interface: Table Fields for DDIF_FIELDINFO_GET |
|DISVARIANT |Layout (External Use) |
|DOKHL |Documentation: Headers |
|DPPROPS |General property structure for data provider |
|DTC_S_LAYO |Structure for Design of Double Table Control |
|DTC_S_TC |Structure for table controls in the double table dialog box |
|DTC_S_TS |Tab Title Structure |
|DYNPREAD |Fields of the current screen (with values) |
|E071 |Change & Transport System: Object Entries of Requests/Tasks |
|E071K |Change & Transport System: Key Entries of Requests/Tasks |
|EAPS_20 |Field Enhancements for EA-PS 2.0 |
|EDIDC |Control record (IDoc) |
|EDIDS |Status Record (IDoc) |
|EDIFCT |IDoc: Assignment of FM to log. message and IDoc type |
|EDIMESSAGE |Transfer Structure with all Sy Fields for T100 |
|EDI_DS |Status record for interface to EDI subsystem |
|EDI_HELP |Help Structure for Reference Fields in EDI Function Groups |
|EK05A |Communication Area Purchasing - Financial Accounting |
|ESKN |Account Assignment in Service Package |
|EUDB |Development Environment Objects |
|EUOBJ |Workbench: Development Objects |
|EXCLTAB_LINE |Lines of EXCLTAB with OK Code to be Deactivated |
|EXISTING_DOC |Original Document |
|F05ACTRL |Control Fields for SAPMF05A and Subprograms |
|FAGLBSEGL_S |Additional Sender Flds from General Ledger for Doc. Overview|
|FAGL_GLT0_ACCIT_EXT |Line Information for Document Splitting |
|FAGL_MIG_S_BUKRS_LEDGER |Combination of Company Code and Assigned Ledgers |
|FAGL_SPLIT_FLD_S |Characteristics Permitted for Split |
|FAGL_S_APPLICATION |Application and Subapplication |
|FAGL_S_BALDIM |G/L Characteristics of Document Split in New General Ledger |
|FAGL_S_BUKRS |Structure with Company Code |
|FAGL_S_BUKRS_EXT |Structure: Company Codes --> Ledgers |
|FAGL_S_CURTYPES |Currency Types of a Ledger |
|FAGL_S_MIG_001 |Structure for Table FAGL_MIG_001 & FAGL_MIG_001_S |
|FAGL_S_MIG_MGPLN_EXT |Structure: Extended Migration Plan Information |
|FAGL_S_T8G40_BS |Split Fields with Characteristic "Balance Sheet" |
|FCRD_VBKPF |Credit Card: Include for Appends for BKPF, VBKPF |
|FCRD_VBSEG |Include for Appends for VBSE* |
|FDM_AR_CASE_ATTR_1 |FSCM DM: |
|FDM_AR_LINE_ITEM |FSCM: DM |
|FDM_AR_RFPOS |FSCM-DM: Enhancemt of Line Item Disp. with Dispute Case Flds|
|FELD |Screen Painter fields (internal) |
|FICCO |Adjustment Values for External Document Items |
|FICCT |Totals Information for Interclient Posting |
|FICTX |Tax Information for ICT |
|FIELDINFO |Field attributes for a specific field |
|FIN1_PARAM |OBNG: Trans. structure for official doc. numbering (global) |
|FIN1_PARAM_FI |OBNG: FI parameters |
|FIN1_PARAM_MM |OBNG: MM Parameters |
|FIPEX_STRUC |Subfields Commitment Item |
|FIPOEXT |Help structure for line items to be generated automatically |
|FIREVDOC |Transfer Structure for Dialog Module FI_DOCUMENT_REVERS |
|FISTL_STRUC |Substructure Fund Center |
|FM01 |Financial Management Areas |
|FMBLSTRING_COMPONENTS |Component of the BL String |
|FMCI |Commitment items master data |
|FMDY |FIFM: Screen Fields |
|FMFCTR |Funds Center Master Record |
|FMFG_ACCIT_EXTENSION |Extention for all fields that have to be transfered into BL |
|FMFINCODE |FIFM: Financing code |
|FMFPO |FIFM: Commitment Item |
|FMHRBA_NEG_DOC_TYPES |HR Integration: Doc. Types for Negative Funds Commitments |
|FMHRBA_SETTINGS |Integration with HR: Settings |
|FMHRBA_VAD_SETTINGS |HR Integration: Generate Value Adjustment Docs for Changes |
|FMICCN |FM: Append Structure for FMIOI (CCN Fields) |
|FMIDATA |Common Data for Funds Management Actual Data |
|FMIDATAFI |Clean FI Data for Funds Management Actual Data |
|FMIDATAOI |Clean Open Item Data for Funds Management Actual Data |
|FMIFIIT |FI Line Item Table in Funds Management |
|FMIKEY |Common Key for Funds Management Actual Data |
|FMIKEYFI |FI - Key for Funds Management Actual Data |
|FMIKEYOI |Common Key for Funds Management Actual Data |
|FMIOI |Commitment Documents Funds Management |
|FMIOIKEY |Key for Table FMIOI |
|FMIOI_USFG | SD order needs quantity |
|FMIREF |Ref. Funds Management Actual Data to Preceding Document |
|FMISPS |General Parameters for Funds Management |
|FMIT |Totals Table for Funds Management |
|FMMRESERV |Include for the Reduction of Funds Reservations (FM) |
|FMRFC |Function Modules and their RFC Destinations |
|FMSP_SPLIT_FIELDS |PSM Fields used in multiple account splitting |
|FMT001 |Additional Customizing for Funds Management |
|FMUP00T |Update Profiles |
|FMUP01 |Update Control with Value Type Dependency |
|FMUP_INV_KEY |Extension for FM Update: FI Key of Invoice |
|FMUP_PAY_KEY |Extension for FM Update: FI Key of Payment |
|FS006 |Fields for Optical Archiving |
|FTCHECK |Foreign Trade: Import Simulation - Ctrl Fields for Pricing |
|FTEXTS |Communication Structure for Additional Components |
|FTGENERAL |Foreign Trade: General Fields Item |
|FUND_STRUC |Substructure Fonds |
|FVD_TZB0A |Append to TZBOA: Loans Fields |
|GLACCOUNT_CCODE |G/L Account Master Record: Company Code |
|GLACCOUNT_CCODE_DATA |G/L Account Master Record: Company Code - Data |
|GLACCOUNT_CCODE_INFO |G/L Account Master Record: Company Code - Information |
|GLACCOUNT_CCODE_KEY |G/L Account Master Record: Company Code - Key |
|GLX_ORG_INFO |Organizational Assignment |
|GMBSEGZ |Grants Management Add-on |
|GXXLT_H |XXL interface: horizontal features |
|GXXLT_O |XXL_interface: texts for online display |
|GXXLT_S |XXL interface: structure of the semantics table |
|GXXLT_V |XXL interface: vertical features |
|HELPVAL |Restrict Value Range - Transfer Table |
|HELP_INFO |Transfer Values for the Help Processor |
|HELP_VALUE |Structure or Function Module HELP_VALUE_GET_FOR_TABLE |
|HHM_COBL |Include for COBL from FM |
|IADDR_PSO |Local Authority Additional Fields (Address) |
|IBKPF_PSO |IS-PS: Include Structure BKPF Payment Request Doc.Header |
|ICDIND |Structures for generating change document update programs |
|ICON |Icons table |
|ICONS |Icons |
|ICURR |Interface for Currency Translation
Maybe you are looking for
-
R7970 problem with temperature sensor?
So last month I RMA'd my R7970 and I just received it in the mail. Originally my problem was I had artifacting lines, and occasionally freezes. In the time between that I had ordered a 5450 just as a temporary card. When I got my 7970 back I removed
-
Calculate excise for purchase order line items ( for import only)
Dear all, please help me to calculate excise duty form ( imports only) purchase order for its line item. i can calculate for domestics PO using "BADI_TAX_CONDITION" .\ But I need to calaculate custom duty also . so this BADI does not work . So, pl
-
Selecting a column goes for a full table scan
Hi, Oracle version 10.2 I have the below query: SELECT c.companyid, c.contactid, c.contactlname FROM contact c,company ic WHERE UPPER((c.contactlname)) LIKE CASE WHEN 'test' IS NULL THEN UPPER((c.cont
-
Question for Kensington Orbit Trackball Owners
Just bought the Kensington Orbit Trackball and would like to know if it is necessary to Install software for it. I had assumed that it was plug and play. (as far as regards the MacMini) Thanks.
-
Hi all. I recently replaced my old AirPort Express (802.11g) with an AP Extreme (802.11n). When using the express, I had a Lexmark E232 connected to it and was easily able to print from any computer which connected to the network. But since I have up