Configuration to setup approval for vendor changes and creation

Can anyone help to know where to switch on the approval for vendor changes and creation?

Just a quick thanks that it worked, aesiris.
Also on the that page: https://wiki.archlinux.org/index.php/Po … Management
i2c device power management can be managed with very much the same rule structure:
ACTION=="add", SUBSYSTEM=="i2c", TEST=="power/control", ATTR{power/control}="auto"
Can't for sure say the same for spi devices, since I apparently have none. I'd edit that page, but I can't.

Similar Messages

Change pointers for Vendor, Material and GL Posting

Hi Experts ,
when something changes or an event takes place in SAP, i want that information to be sent out to their
external systems for Integration purposes.
Can anyone advise me what kind of steps and configations for Vendor, Material and GL Posting need to be done step by step .
Pls.help me in this regards as it is very much required .
Regards
Kiran

Please respond anyone

Configuring double invoice check for vendor invoices posted through FB60

Dear all
Can anyone tell me how to configure double invoice check for vendor invoices posted through FB60.
for miro documents..we can use Tcode OMRDC
Is there any such tcode which can be used for configuring fi invoices for double checking..
regards
Expertia

Dear Expertia,
In FI,when checking for duplicated invoices, the system compares the
following :Vendor, currency, company code, gross amount of the invoice,
reference document number and Invoice document date.
SAP Note 305201 clarifies this in a more details; please read it.
The following fields must be identical for Duplicate invoice check
     Company code                              (BUKRS)
     Vendor number                             (LIFNR)
     Currency                                  (WAERS)
     Reference number                          (XBLNR)
     Amount in document currency               (WRBTR)
     Document date                             (BLDAT)
If the document is having any one of the above filed different then the
system does not consider it as a duplicate invoice.
Also It will check duplicate invoice check in vendor master data and
in posting key is there check box selected for sales related
The setting you making in OMRDC i.e Materials management->Logistics
Invoice Verification->Incoming Invoice ->Set Check for Duplicate
Invoices is only valid for MM and not FI invoices posted via FB60/FB65
You should check the F1 help on field "Chk double inv." (LFB1-REPRF)
in the relevant vendor master record (transaction FK03).
Please also check, that message F5 117 has been set correctly in the
IMG using this path:
Financial Accounting -> Financial Accounting Global Settings ->
Document -> Default Values for Document Processing -> Change Message
Control for Document Control For Document Processing
Finally & mainly, go to the relevant posting key is defined as sales
related in transaction OB41. You have to flag this field if the
duplicate invoice check should work.
I hope this helps You.
mauri

Working on IDOC OUTBOUND FOR Vendor Master and Customer Master

Hi Group,
I need to create IDOC's for Vendor master and customer master using ALE. Whenever they create vendor/customer or changes to vendor/customer should create IDOC's.
Can anyone please help me out how to proceed? I know that we can use CREMAS/DEBMAS and CREMAS04/CREMAS...But I would like to know how to use those.
Thank-You,
Venky

Hi Sai,
Welcome to group.
Related to CREMAS/DEBMAS, for your situation, you can use the change pointers. With this, when ever there is an change/create, it will create an entry in CDHDR & CDPOS and based on that it will create the IDOCs for these.
Activate the change pointers for these message types and run the application RBDMIDOC periodically (whenever you want). This application will create the IDOCs based on your entries.
To activate the change pointers, the TCODEs are
BD50 Checking change pointer is activated for Message Type
BD52 Checking which fields are configured change pointer to create. (please make sure, an entry will exist in BDCP table)
I hope you know the remaining configuration related to partner profile entries (WE20) i.e. to which system you want to send the idocs and Inbound or Outbound etc.
Let me know if you need further info.
shylesh

Approval for Vendor Invoice

My client required Approval for Vendor Invoice Payment from senior person. How can i configured this scenario in sap AP?
Pls Reply

Hi,
Please check this link:
[Workflow for Payment Release|http://www.google.co.in/url?sa=t&rct=j&q=workflow%20for%20payment%20release%20sap&source=web&cd=1&ved=0CBsQFjAA&url=http%3A%2F%2Fhelp.sap.com%2Fprintdocu%2Fcore%2FPrint46c%2Fen%2Fdata%2Fpdf%2FFIBP%2FFI-AP-AP-RP.pdf&ei=QdjETqe6Ds-xhAfv6NSEDg&usg=AFQjCNGlK2kUdPUyvPIgG32Ulni3ks9tuA&cad=rja]
Regards,
Jigar

Approval for Vendor Bid

Hi All,
I have activated "WS79000010"- No approval required for vendor bid and maintained the required start conditions for this workflow, but when the vendor submits the bids the system throws an error that " No approval workflow found. Inform system administrator".
We are using SRM 5.0 with SP09
Any inputs on this issue are highly appreciated.

Hi,
Please check your starting conditions.There seems to be some problem with that as the system is unable to identify the workflow to be triggered.
Also see teh foll note and related threads for more pointers;
Note 865269 - Bid: Incorrect workflows, incorrect approval preview
Re: Err "No workflow found" while creating bid
Re: URGENT : Workflow for Vendor Bid
Re: Urgent: Quotation Workflow: Message Approval WF is ambiguou
BR,
Disha.
<b>Pls reward points for useful answers.</b>

Can u tell me any predefined BAPI for change and creation of Material

Hi,
Can anybody tell me predefined BAPI for change and creation of Materialmasterand Pricing?
Thanks & regards,
Gopianne.

you can use the BAPI to BAPI_MATERIAL_SAVEDATA create as well as to change material master.
When changing material master data, you need enter only the material
number.
In the header data, you must select at least one view for which data is
to be created. Depending on the view selected, you must maintain other
required parameters. If you do not enter values for all of the required
parameters, the method is ended with an error message.
The corresponding fields in the tables (such as CLIENTDATA) must first
be supplied with data by the calling program. An indicator must also be
set for each of these fields so that the data is written to the database
by the method. This requires the calling program to supply the
corresponding field with the indicator in a checkbox table (for example,
CLIENTDATAX). Checkbox tables exist for tables that do not contain any
language-dependent texts (MAKT, MLTX), International Article Numbers
(MEAN), or tax classifications (MLAN). Several data records for a
material can be created in these tables.
regards
vivek
reward points if it helps

Wht r the standard tables for vendor customer and sales order report/

Hi wht r the standard tables for vendor and customer reports and is how in normal we cannot use them for vendor reporting and etc ?

Hi
Customer is related to Sales Module
So for a customer we fetch the reports of Sales orders , Deliveries and Billing doc's
CUstomer and Vendor related tables with important fields:
KNA1: Customer Master-General(KUNNR,NAME1,LAND1)
KNB1: Customer Master(Company Code)(KUNNR,BUKRS,PERNR)
KNC1: Customer Master Data (Transaction Figures)(KUNNR,BUKRS,GJAHR)
KNVK: Customer Master Contact Partner(PARNR,KUNNR,NAME1)
KNVV: Customer Master sales data(KUNNR,VKORG,VTWEG,KDGRP)
KNBK: Customer Bank Details(KUNNR,BANKS,BANKL,BANKN)
KNVH: Customer Hierarchy (HITYP,KUNNR,VKORG,VTWEG,SPART)
KNVP: Customer Master Partner Functions(KUNNR,PARVW,KUNN2)
KNVS: Customer Shipment data(KUNNR,VSTEL,TRANS)
KNVI: Customer Tax data(KUNNR,ALAND,TATYP)
LFA1: Vendor Master-General (LIFNR,NAME1,ORT01)
LFB1: Vendor Master(Company Code)(LIFNR,BUKRS,PERNR)
LFC1: Vendor Master (Transaction Figures)(LIFNR,BUKRS,GJAHR)
Sales related Tables for a customer
VBAK: Sales Document(Header Data) (VBELN, KUNNR)
VBAP: Sales Document(Item Data) (VBELN,POSNR,MATNR,ARKTX,CHARG)
      Enquiry, Quotation, Sales Order are differentiated based on Doc.
      Type(VBTYP field) in VBAK,VBAP Tables( for Enquiry VBTYP = A,
      for Quotation 'B' & for Order it is 'C'.)
LIKP: Delivery Table (Header Data)(VBELN,LFART,KUNNR,WADAT,INCO1)
LIPS: Delivery Table (Item Data)(VBELN,POSNR,WERKS,LGORT,MATNR,VGBEL)
      (LIPS-VGBEL = VBAK-VBELN, LIPS-VGPOS = VBAP-POSNR)
VTTK: Shipment Table (Header Data)(TKNUM)
VTTP: Shipment Table (Item Data)( TKNUM,TPNUM,VBELN)
      (VTTP-VBELN = LIKP-VBELN)
VTFA: Shipping Document Flow(TKNUM,VBELV,VBELN)
VTPA: Shipping Partners data(VBELN,PARVW,KUNNR,PERNR)
VTTS: Stages in Shipment(TKNUM,TSNUM,TSTYP)
VTSP: Transport Stage/Shipment Item Allocation(TKNUM,TSNUM,TPNUM)
VEKP: Handling Unit: Header(Packing)(VENUM,VSTEL)
VEPO: Handling Unit: Item (Packing)(VENUM,VEPOS,VBELN)
VBRK: Billing Table(Header Data)(VBELN,FKART,BELNR)
VBRP: Billing Table(Item Data)(VBELN,POSNR,FKIMG,NETWR,VGBEL,VGPOS)
      (VBRP-AUBEL = VBAK-VBELN, VBRP-VGBEL = LIKP-VBELN)
      Apart from these tables there are lot of other tables which starts with
      V, but we use the following tables frequently.
VBUK: All Sales Documents status & Admn. Data(Header)(VBELN,VBTYP)
      VBTYP= C(Sales Order) VBTYP=J(Delivery) VBTYP=M(Invoice)
VBUP: Sales Documents status & Admn. Data(Item)(VBELN,POSNR)
VBEP: Sales Doc. Schedule Lines Data(VBELN,POSNR,EDATU,WMENG)
VBKD: To get sales related Business data like Payment terms etc.(VBELN,ZTERM)
VBFA: sales document flow data(VBELV,VBELN,POSNV,VBTYP)
VBPA: Partner functions Data(VBELN,PARVW,KUNNR,LIFNR)
VEDA: Contract Data(VBELN,VPOSN)
VEDAPO: Contract Data(VBELN,VPOSN)
Vendor related MM tables
EBAN-- Pur.Reqn. Data (BANFN,BNFPO,BADAT,MATNR)
EBKN-- Purchase Requisition Account Assignment(BANFN,BNFPO,VBELN)
EINA- Purchase Info.Record (General Data)(INFNR,MATNR,LIFNR)
EINE-- Purchase Info.Record (Pur.Orgn Data )(INFNR,EKORG)
ELBK-- Vendor Evaluation Header Data(LIFNR,EKORG,KLASS)
EKKO-- Purchase Order Data (Header)(EBELN,BSTYP,BSART)
EKPO-- Purchase Order Data (Item)(EBELN,EBELP,MATNR)
       RFQ and PO are differentiated by Doc Type(BSTYP)in EKKO table.
       For RFQ it is A and for PO it is F.
MKPF-- GRN Data (Header) (EBELN,BLDAT,BUDAT,XBLNR,BKTXT)
MSEG-- GRN Data (Item)(MBLNR,BWART,LIFNR,MATNR,EBELN)
       Apart from this there are lot of tables which begin with 'M'& 'E', but we
       use the following very often.
EKBE--PO History Data (EBELN,EBELP,BELNR,BLDAT,MATNR,VGABE)
EKBZ--PO History with delivery Costs(EBELN,BELNR,LIFNR,XBLNR)
EKET--Schedule lines data of a PO (EBELN,EINDT,SLFDT)
EKES--Vendor Confirmations Data(EBELN,EBTYP,EINDT,XBLNR)
Reward points if useful
Regards
Anji

Trying to setup airport for 1st time and it will not connect to internet, we also did not create a new network and cannot find this option again

Trying to setup airport for 1st time and it will not connect to internet?

You might try doing a reset of your AirPort unit. Use a pen or paper clip to press in on the recessed reset button while you plug it in, then continue to keep the button pressed until the status light flashes several times,
For more advice, please describe all your networking gear.

Bapi For creation and change for Vendor Master and Customer Master

I am looking for BAPI to create and change Vendor Master and Customer Master which will not take me to standard SAP transaction but will work in the background
Explanation: BAPI to delete material (BAPI_MATERIAL_DELETE) take you to standard SAP screen of T-Code MM06 but BAPI to create material (BAPI_MATERIAL_SAVEDATA) creates material in the background i.e. does not take you to standard SAP screen of T-Code MM01
So in my case (i.e. to create and change Vendor Master and Customer Master ) I want BAPI which would work like BAPI to create material (BAPI_MATERIAL_SAVEDATA)

For general information,to find BAPIs associated with any business object :
Transaction : BAPI - choose alphabetical tab - Find customer - (right side choose - tools - create bapi list and search ) , you will get all the BAPIs associated with this particular business object
Mathews

Setup Help for 2 Wireless and 1 Wired Router!

Hello,
I hope this is the appropriate forum for this request. I am helping a neighbor who has just come out of the hospital. Since he will be homebound for quite sometime, he needs to enhance his home network. I offered my help and now I am looking for some assistance. :-)
Currently he has DSL which goes from his DSL modem into Linksys WRTG54G v2 router in a basement. The wireless signal does not travel very far. Fortunately there are 3 ethernet jacks that are present. Two of those jacks run to an office on the first floor, the third runs to the office on the second floor.
Additional equipment we have are a Linksys BEFSR41 v2 wired router and another WRTG54G v6 wireless router. On the 1st floor there are 3 devices which need to be connected (a PC, a Mac and an HP printer) and the second floor is where he will be roaming with the laptop.
Given this, my guess the best setup would be:
Basement the wired router running to the three ethernet ports (2 on the first floor, the third on the second floor).
On the First floor, use on of the ethernet extensions to connect the wireless router. Then from the router ports, connect to the 3 devices (PC, Mac, HP printer) via ethernet. This will also send out a wireless signal if a wireless device (laptop) in the vicinity.
Then on the second floor, plug the other wireless router into the ethernet port and have it emit the wireless signal.
I should note that the second floor is really the only floor which is essential to have the wireless signal
So my questions are this:
1a)Could the above scenario actually work?
1b)Is there are a better setup then what I thought
2a)I imagine that I will need to change the IP for two of the devices from 192.168.1.1 to something like 192.168.2.1 and 192.168.3.1, correct?
2b)In addition I will need to disable DHCP on 2 of the 3 routers, but which one? I imagine that one on the second floor?
3) What else do I need to do?
Thanks in advance!

yes , you can certainly use that kind of a set up...
BEFSR41 in the basement......if you are configuring the wireless router on the first floor for an ethernet to ethernet connection , the ip add on it should be 192.168.1.2 and disable the dhcp....if you go for an ethernet to internet connection then the ip address of the wireless router should be 192.168.2.1....no need to disable the dhcp....
similarly configure the wireless router on the 2nd floor...if an ethernet to ethernet connection then ip add - 192.168.1.3 and dhcp is disabled....and if ethernet to internet connection , then ip add 192.168.3.1....
make the wireless settings unique for each router and so that ensure whether you are connecting to the 1st router or the 2nd router.....

Article to setup Extreme for N only and optimize settings?!?!

I just replaced an older b/g AIrport Extreme with a newer dual band N version of Airport Extreme. I also replaced my Express b/g with an N version as well. I have the Extreme connected to my Verizon FIOS modem by ethernet and manually configured to "bridge" mode with the goal of maximizing the FIOS speed that can be obtained (versus extending the FIOS wireless network from the Verizon router). I am totally confused about what steps to take to ensure that my new "bridged" network with the Extreme and, subsequently, the Express, only use N and not a/b/g WiFi for the network. I have Airport Utility v5.5. Is there an article or another post that goes through this step by step... for dummies I have found a bunch of posts that address this general topic, but the feedback provided to the OP is usually assuming I know some piece of info that I just don't actually know... one step ahead of me. Thanks for any guidance or feedback to point me in the right direction!

You mentioned in your post that you had manually configured the AirPort Extreme (AEBS) to act as a “bridge” for your Fios router, so I assume that you have likely already configured some other aspects of the AEBS at this time, so I will not go into a lot of detail on some items that are normally fairly intuitive.
If you have not already installed the software that came on the CD with your AEBS, it would be a good idea to do so as some of the most recent dual band products are using a version of AirPort Utility that is not yet available for download from Apple’s site and its also likely that you have a more recent version of the firmware for the AEBS which is also not available for download.
In general, I think it helps most users to temporarily connect an ethernet cable from their computer to one of the LAN <-> ports on the AEBS to configure the device rather than trying to use wireless. So, if you are having difficulty with wireless in trying to configure the AEBS, use the ethernet option.
Speaking of ethernet, you mentioned that you wanted the best performance possible for your network and that would start with the ethernet cables. Make sure they are either CAT5e or CAT6 cables to take advantage of the Gigabit speeds that the AEBS is capable of handling.
Open Airport Utility and click Manual Setup
Click the Base Station tab below the row of icons to enter a name for your device and a device password along with time and time zone settings
Next, click the Wireless tab next to the Base Station tab to display the wireless settings page
Wireless Mode would be Create a wireless network
Wireless Network Name is your choice
Put a check mark in the box next to Allow this network to be extended
Radio Mode should be 802.11n only 5 GHz to provide the fastest speed possible.
You may need to hold down the “option” key on your computer while you click on the selection box to display all the available choices. If you later find that the 5 GHz setting does not penetrate as well as hoped, you will need to return to this area to change the setting to 802.11n only 2.4 GHz
Channel…hold down the option key again when you click on this box. Select one of the higher numbered channels.
Wireless Security would be WPA2 Personal
Wireless Password is your choice
Click the Wireless Options button and make sure there is a check mark next to Use Wide Channels and click Done
Click the Internet icon in the row of icons and check the Connection Sharing setting at the bottom. It should be set to “Off (Bridge Mode)”
Click Update at the lower right and the AEBS will restart in 20-30 seconds and the light should turn green.
Now, take your Macbook and test to make sure that you can get a good internet connection near the AEBS. If so, move your Macbook to the room and position it as close as possible to the location where the AirPort Express (AX) will be installed and check to make sure that you get a good internet connection.
Hold down the “option” key on your computer while you click on the fan shaped Airport icon at the top of your screen. Look for the Transmit Rate number and jot that down for future reference. Move your Macbook around to other locations between the AEBS and the AX location and you will see that the Transmit Rate changes. It will be higher near the AEBS and will fall off as you move away from the AEBS.
Also, please download Air Radar and use the Scan feature at the lower right of the window to get a different look at the signal strength of your AEBS network. Air Radar is not free, but there is a 15 day trial period. Look at the Fios network as well in terms of signal strength where the AX will be located.
You can also use Air Radar to locate any other visible wireless networks in the area to help identify them in case you experience wireless interference issues.
At the tentative AX location,
What is the Transmit Rate that you see?
How strong is the signal from the AEBS in terms of percentage using Air Radar?
How strong is the signal from the Fios router in terms of percentage using Air Radar?
If you connect your Macbook to the Fios network, can you get a Transmit Rate number for that?
Please post back on your results and any questions you have to this point and we’ll decide how best to tackle the “extend” challenge. There will likely be some compromise choices to be made on this next step.

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

Standard interfaces for vendor invoice and salary posting

Hi all,
Our customer is asking for a standard interface for vendor invoices (not purchase invoices, only for invoices entered in FB60), if they could have a CSV file from vendor and import that to SAP. Is there a standard functionality or do we have to build an own interface?
They also ask if there is a standard interface for salary file so they can tell the company that create the salary file that they should use a standard format or do we need o to create an interface there to?
Thanks in advance!
BR L

Hi,
You can either go with INVOICE01 or INVOICE02, As per the requirement you can check with the Function module attach with the idoc type, and whether it is providing the appropriate functionallity or not.
Thanks & Regards,
Navneet Chaubey

BAPI for Vendor Invoice and Credit memo - FB60

Hi
Iam using BAPI_ACC_DOCUMENT_POST for creating Vendor invoice and Credit memo ..Could you please tell me which fields to be populated on the below structures?
what will be the value i should use for BAPIACHE09-BUS_ACT...RFBU or RMRP?
ACCOUNTPAYABLE ( BAPIACAP09)
ACCOUNTGL(BAPIACGL09)
CURRENCYAMOUNT( BAPIACCR09)
Only the fields which needs to be populated on these structures when we do FB60 invoice and credit memo using bapi..
Thanks in advance
Govi

Hi,
Populate in Document_header : (User name, Comp code, Doc DAte, Doc type, Ref Doc No)
                   Account GL : ItemNo_Acc, GL Accuont, REf Key1, Refkey2, Refkey3, Account Type = 'A', Doc Type, Comp code
                                          Account_number, Cost_center
                   Account Payable: ItemNo_Acc, Vendor_No, Rey_key1, Ref_key2, Ref_key3
                  Currency Amount: Item No_Acc = 2, 1
                                                Curr = USD, USD
                   Amt_Doccur
At last use commit bapi.
Thanks,
Krishna

Configuration to setup approval for vendor changes and creation

Similar Messages

Maybe you are looking for