Vendor maintenance

Hi
Can anyone clarify me on the below issue. I was using a particular vendor 05 for a logical " X" system and against a particular purchase org unit.
Now I have defined another root in the same org structure and with as the backend client got changed so the same above o5 vendor is present in this backend also.I wanted him to extend to this backend also with the same Purchase org.
This is SRM4.0 version. I have gone to BBPMAININT and in the orgunit I have given the new Purchasing org unit defined for the new struct. but still I am not able to see this vendor has been extended with this new logical system and new Purorg.
please clarify me.
Regards
Srujan K

>
srujan K wrote:
> Actually this was SRM 4.0 Version and I have the Root org node under that same node there is a company code node and under same node I have this suppliers node also point one backend system assuming" X" .
> Now client has some problems in maintaining this "X" backend system so they have replaced this "X" backend with " Y"
>(...)
So, unique backend is 'Y' ?
>
srujan K wrote:
> So the required config for " Y" backend system to establish the connection between SRM and R/3 is done and Org struture is build respectively and another Root for suppliers is setup.
>(...)
Why did you ceate a new organizational unit root node for your suppliers ? You can use the existing one.
I don't have a SRM 4 release in front of me, so i don't remember if for the vendor root node you have a Backend logical system reference. If yes, just switch to the new one.
>
srujan K wrote:
> But then when I try to replicate the vendors using BBPGETVD system says this Business partner already exists and In the venmap table I can see this Vendor with Old SAP R/3 client.
>
> So in the BBPMAININT I have gone and added the new Pur Org unit number and maintained the PO currecy , terms of payment and etc.
> But still I am not able to find this vendor against the new R/3 client.
>(...)
If you cannot extend your vendors from logical system LS1 to LS2 (i guess purchasing organization concerned has same code for both R/3 Backend - old one and new one) neither with BBPGETVD transaction nor BBPUPDVD, then run BBP_UPDATE_MAPPING transaction: here, fill-in frame to "Add/Change/Delete Backends" according to your need. All existing vendors will be updated.
>
srujan K wrote:
> But somevendors are there who exists for both clients. I mean if a vendor A is there he will be displayed in the Venmap table with reference to " X" logical system as well as " Y" logical system also.
>
>So If I wanted to make each or selected number of vendors to appear in the VenMap table against both the logical systems what shouild do?
>(...)
See above.
Regards.
Laurent.

Similar Messages

ECATT for FK02 Vendor Maintenance Bank Details - Error

Hello Forum,
I have been trying to record an eCATT via TCD Recording for the FK02, Vendor master record change transaction. Every time I get to the Simulation Screen "SAPMFO2K 0130" to insert the parameters, I receive the error below. I only receive the error on this screen.
Does anyone know why this could be happening?
Thank you,
Isis
Runtime Errors         DATA_BAD_REFERENCE
Date and Time          03/25/2010 13:50:39
What happened?
Error in the ABAP Application Program
The current ABAP program "SAPLECATT_DYNSIM" had to be terminated because it has
     come across a statement that unfortunately cannot be executed.
Error analysis
When accessing a reference variable, an invalid value was detected.
Trigger Location of Runtime Error
     Program                                 SAPLECATT_DYNSIM
     Include                                 LECATT_DYNSIMU05
     Row                                     107
     Module type                             (FUNCTION)
     Module Name                             ECATT_FREE_SIMULATION_DATA

I have a same question and look forward to the final solution.
OK,You can set the import parameters manually instead of screen simulator,then it solved.
Edited by: Lykin on Sep 8, 2010 3:28 PM

Vendor Maintenance screen display when posting in FB01

Hi All,
I would like to ask your idea if ever you have encountered this issue.
In FB01 I post a document using the vendor 999999 after entering the posting key and press the enter. Another screen displayed..that screen looks like the transaction FK01. It seems that you need to recreate again the vendor. But my question is why did that screen appears though that vendor is already created..What are instances that this screen will appear..
Regards,
Ekitzv

Hi,
That vendor must be One-time vendor.
The concept of one time vendor is that, there is a single transaction with that vendor, like Fly-Ins.. and which are not regular.
So, SAP has given you the facility to create a Vendor in the Account Group One time vendor, which will have one vendor Account No., in your case it is 999999, and whenever you post entry with this vendor Account No., then, at the time of posting entries, a pop up screen will come for you to enter the name, city etc..
The balance vendor master data, like pmt terms, Recon account remains same for all, but only the name & city changes..
So, instead of creating many such one time vendor code in the system, you create just one code and then on a case to case basis, you post liability in this vendor, and enter name ,city etc.. at the time of Invoice booking.
=========
When you go to FK01 to create a vendor, press F4 on Account Group, and you will see that there is a check mark for OTA(One time acount), with this tick, you can identify that whether your vendor 999999, is in the account Group OTA.
Hope it helps..
Regards,
SAPFICO

Customer & Vendor not transported via Plant tCodes WB01/2 or WB07/8

Hello,
We have change control enabled in our Dev, instance/clients SAP 4.7 IS-Retail , Basis 6.2
Looking for help in understanding the necessary steps to transport the Plant Vendor and Customer records.
The transport includes Plant records, but in the destination client the Customer and Vendor records that
are automatically created via WB01/02 are not being included in the transports?
Would appreciate any advice on how we transport the Vendor and Customer records that automatically
get created via WB01/2 in the source client to the destination client.
If we try to use XD01, XK01 the system enforces the Customer/Vendor records can only be maintained
via the WB## transaction codes for IS-Retail.
Have tried using WB07/08 and included in a transport, but still the Customer & Vendor master records
are not being included in the transport.
Any ideas?
Regards, Ron.

WB02 can not be used if the Customer and Vendor are not created implicitly via WB01, this
is why the transport methodology is failing, See below. We were able to use WB01 on an existing
Plant that had been transported, to maintain/create the Customer and Vendor relationship,
but this produced inconsistent CO relationships that caused ME59 to fail.
Note, you can not use XD01/XK01 for Customer/Vendor maintenance as it would pertain
to Plant Customer Vendor relationships, this must be done via WB## t-codes.
What we have found is that exporting and importing plants includes the Customer & Vendor
coupled to the Plant. However the export and import WBTE,WBTI capability is not working
properly as is similar to the transport capability.
So, we have reverted to manually creating the Plant in each Instance Dev "IMG Gold Client",
Test, Pro to complete this requirement. This has proven to work, but transports and or
export/import have proven to not work as expected. Probably specific issue with SAP
IS-Retail.

Order of Precedence in Field Selection settings for Vendor Master

Hi,
There are three transactions which help define the list of mandatory, optional, suppressed and finally display only fields during vendor maintenance.
These are,
OMSG -> Define Account Groups and Field Selection( Vendor)
OMFK -> Define Screen Layout Specific to Purchasing Organizations
OMSX -> Define Transaction-Dependent Screen Layout.
All these settings are independently maintained.
In case of conflicting settings, say for example, Field Name 1 is made mandatory with tcode OMSG, but suppressed with tcode OMFK, how does the Vendor transaction(XK01, FK01, MK01) behave.
How are these conflicts resolved ?. Is there any order of precedence.
Regards,
Jeron

Hi,
If both purchasing organizations have separate account group then you can very well achieve in customizing otherwise you need to control it in exit SAPMF02K
Regards
Melih

Vendor Master (XK01) Screen Exit

Hi,
Can you please help me how to add extra screen fields to standard screen i.e.,vendor master (XK01) screen.
Is there any screen exit for XK01 ? OR
Is there any BADI'S for XK01 screen exit ?
Bye
Praveen.

I am looking for a way to use the Vendor Maintenance Program SAPMF02K (XK01/XK02/XK03) to update custom LFM2 fields.
Since there are multiple LFM2 plant(WERKS) Records for a Vendor/Purchasing Org, How can the screen be configured to narrow in on the desired LFM2 record to update?
Goal-Have the additional field appear on the SAPMF02K vendor plant purchasing data screen (330) or as separate button on the alternative data plant screen (341).
Presently I can prompt for the plant and update the existing record, however this is not useful in view mode as the plant field is read only. It also does not look/feel like SAP's XK0x transactions.
Following SAP Note 580266 I was able to use VENDOR_ADD_DATA and VENDOR_ADD_DATA_CS use the custom screen.

UK CIS Scheme: Withholding Tax ID field in Vendor master is greyed out

Following SAP Note 1003730 and the related document UK CIS - Legal Changes Implementation - the notes say that the Subcontractor Verification Number should go in the W/tax Id field (LFBW-WT_WTSTCD) in the vendor master maintenance Withholding Tax screen. We have Extended Withholding Tax activated, but in the WT screen in the vendor master the W/tax Id field has no title and is greyed out in the table control - so you can't enter anything in it.
Has anyone else come across this and found a solution?
Thanks.

Field is visible in XK02 (Central Vendor Maintenance) but not FK02.

FSCM 9.0: Operator Profile Indicates You have No Authority to Enter Vendor

Folks,
Hello. I am working on FSCM 9.0 and login User ID is VP1. I want to add new Vendors' information into the Vendor module. when I click Vendor > Add, the message comes up as follows:
" Your operator profile indicates that you have no authority to enter Vendors. Contact your system administrator."
My login user ID is VP1. I have checked PeopleTools > Security > User Profile for VP1 and add all of Roles into VP1.
But the above problem is still not solved.
Does any folks understand to solve the above problem ? Thanks.

Go to Setup Financials/Supply Chain->Common Definitions->User Preferences->Define User Preferences
Select the VP1 userid, then under Product Preference select Procurement. There should be a hyperlink for Vendor Processing Authority.
You can also check the underlying table, PS_OPR_DEF_TBL_VND, the column is AUTH_VNDR_UNCERTFY, or run the User Preferences Report and select Report on All Products and Report on All Users, then scan the output for Vendor Maintenance to see which users already have authority to enter.
Regards,
Bob

Oracle Document Capture Indexing Macro

Hi,
Hi,
Im trying to populate my Feild Name workflow based on the Type Field and subtype Field that is selected by an end user.
I've coded this in an ODC macro but it look like ODC the code is only validating the line of if statement and populating that value.
I looking for the direction i should take to make odc validate each statement and if the crieteria is met then it should populate that value. i've attached a sample of the code.
You help is greatly appreciated.
Below is a sample of the Code
Option Explicit
' * Sample Index macro that will allow for Index user to change the patch code on an image within a batch by using a
' * hot key. The user can hit the F10 key to change an image's Patch Code attribute from no patch code to Patch
' * type II for example, then change it back to no patch code by marking the same keystroke. The macro can be
' * modified to use different patch codes by changing the PATCH_VALUE constant to one of the patch code constants
' * listed (e.g. PATCH_I, PATCH_II, PATCH_III, PATCH_IV, PATCH_VI, PATCH_T). The string displayed underneath
' * the thumbnail image can be modified by changing the value for the constant PATCH_STRING. The hotkey (F10 by
' * default can be changed to another key by changing the HOT_KEY_VALUE constant.
' * Modified by VICOOK - 1/21/2011
' * Modified by PHAN - 1/31/2011 - Added the Increment by Separator Sheet Macro
' Patch code constants.
Private Const PATCH_I      As Integer = 8 ' "Patch Code I value"
Private Const PATCH_II      As Integer = 2 ' "Patch Code II value"
Private Const PATCH_III As Integer = 1 ' "Patch Code III value"
Private Const PATCH_IV As Integer = 16 ' "Patch Code IV value"
Private Const PATCH_VI      As Integer = 32 ' "Patch Code VI value"
Private Const PATCH_T      As Integer = 4 ' "Patch Code T value"
' These are the references that can be modified to allow for different patch code values and hotkey
Private Const PATCH_VALUE As Integer = PATCH_II              ' This is where you tell the macro which patch code to use for separators
Private Const PATCH_STRING As String = "II"                        ' This constant is the text displayed below the thumbnail when the patch code value has been set
Private Const HOT_KEY_VALUE     As Integer = 121 ' F10 key.   ' This constant is the numeric representation for the key on the keyboard that will allow for setting the patch code
' Global Object references
Private moBatch     As Object
Private moctlIndexing As Object
' Increment by Separator Sheet Merge
Private mlDocID As Long
' Global Variables
Private mnCurrentPage     As Integer
Private Sub SetPatchCodePage(ByVal nPage As Integer)
    Dim oBatchPages     As Object
    Dim oBatchPage     As Object
    Dim bCleared     As Boolean
    Dim bSet          As Boolean
    ' Init the set / cleared vars to false
    bSet = False
    bCleared = False
    ' Grab a reference to the batch pages.
    Set oBatchPages = moBatch.BatchPages
    ' Grab the page.
    Set oBatchPage = oBatchPages(nPage)
    ' Check to see if there is already a matching Patch Code value.
    If oBatchPage.PatchCode = PATCH_VALUE Then
        ' Clear the matching Patch Code value.
        oBatchPage.PatchCode = 0
        bCleared = True
    Else
        ' Apply the patch code value to this page.
        oBatchPage.PatchCode = PATCH_VALUE
        bSet = True
    End If
    ' Persist this page.
    oBatchPage.Persist
    ' If we get this far, inform the user about whether the patch code was applied or cleared.
    If bSet Then
        moctlIndexing.UpdateThumbnailCaptionSuffix(oBatchPage, True, PATCH_STRING)
        MsgBox "Patch Code [" & PATCH_STRING & "] has been applied to page " & CStr(mnCurrentPage) & ".", vbOkOnly + vbInformation, "Patch Code Applied"
    ElseIf bCleared Then
        moctlIndexing.UpdateThumbnailCaptionSuffix(oBatchPage, True, "")
        MsgBox "Patch Code [" & PATCH_STRING & "] has been removed from page " & CStr(mnCurrentPage) & ".", vbOkOnly + vbInformation, "Patch Code Applied"
    End If
    ' Destroy the object references.
    Set oBatchPage = Nothing
    Set oBatchPages = Nothing
End Sub
Public Sub ecIndex_BatchClose()
    ' Destroy the reference to the batch object
    Set moBatch = Nothing
    ' Destroy the refereince to the ctlIndexing object
    Set moctlIndexing = Nothing
End Sub
Public Sub ecIndex_BatchOpen(Batch As Object, IndexingUI As Object, ctlIndexing As Object)
    ' Store a reference to the Batch object.
    Set moBatch = Batch
    ' Store a reference to the ctlIndexing object
    Set moctlIndexing = ctlIndexing
End Sub
Public Sub ecIndex_FieldKeyDown(KeyCode As Integer, Shift As Integer)
    Dim lErrNum          As Long
    Dim sErrDesc     As String
    ' Check to see if the hotkey has been pressed.
    If KeyCode = HOT_KEY_VALUE Then
        On Error Resume Next
        ' Set the Patch Code value on the currently displayed page.
        SetPatchCodePage mnCurrentPage
        If Err.Number Then
            lErrNum = Err.Number
            sErrDesc = Err.Description
            MsgBox "An error was encountered while attempting to apply Patch Code to page " & CStr(mnCurrentPage) & "." & vbCrLf & CStr(lErrNum) & ": " & sErrDesc, vbOkOnly + vbExclamation, "Patch Code Error"
            Err.Clear
        End If
    End If
End Sub
Public Sub ecIndex_PageDisplay(PageNumber As Integer)
    ' Keep track of the currently displayed page during Review.
    mnCurrentPage = PageNumber
End Sub
Public Sub ecIndex_BatchPrecommit(Cancel As Boolean)
Dim oPage As Object
Dim oIndex As Object
' Init the DocID value
mlDocID = 1
' Loop through the batch pages
For Each oPage In moBatch.BatchPages
If oPage.PatchCode > 0 Then
mlDocID = mlDocID + 1
End If
' Assign the numeric DocID value to the "DocumentID" field
oPage.BatchPageIndexes("DocumentID").Value = CStr(mlDocID)
If oPage.BatchPageIndexes("Type").Value = "HR - Benefits" Then
oPage.BatchPageIndexes("Workflow").Value = "Trans-Benefits"
End If
If oPage.BatchPageIndexes("Type").Value = "HR - Employment" Then
oPage.BatchPageIndexes("Workflow").Value = "Trans-Employment"
End If
If oPage.BatchPageIndexes("Type").Value = "Finance - A/P" And oPage.BatchPageIndexes("SubType").Value = "Vendor Maintenance" Then
oPage.BatchPageIndexes("Workflow").Value = "Trans-AP-VendorMaintenance"
End If
If oPage.BatchPageIndexes("Type").Value = "Finance - A/P" And oPage.BatchPageIndexes("SubType").Value = "Payment Processing" Then
oPage.BatchPageIndexes("Workflow").Value = "Trans-AP-PaymentProcessing"
End If
If oPage.BatchPageIndexes("Type").Value = "Finance - A/P" And oPage.BatchPageIndexes("SubType").Value = "A/P Correspondence" Then
oPage.BatchPageIndexes("Workflow").Value = "Trans-AP-CorrespondenceReqMgmt"
End If
If oPage.BatchPageIndexes("Type").Value = "Finance - A/P" And oPage.BatchPageIndexes("SubType").Value = "T&E Vouchers" Then
oPage.BatchPageIndexes("Workflow").Value = "Trans-TE-Vouchers"
End If
If oPage.BatchPageIndexes("Type").Value = "Finance - Accounting" And oPage.BatchPageIndexes("SubType").Value = "Accounting Master Data" Then
oPage.BatchPageIndexes("Workflow").Value = "Trans-GAFA-AcctgMasterData"
End If
If oPage.BatchPageIndexes("Type").Value = "Finance - Accounting" And oPage.BatchPageIndexes("SubType").Value = "Accounting-Payroll Transaction" Then
oPage.BatchPageIndexes("Workflow").Value = "Trans-Acctg-Payroll"
End If
If oPage.BatchPageIndexes("Type").Value = "Finance - Accounting" And oPage.BatchPageIndexes("SubType").Value = "Acctg Correspondance" Then
oPage.BatchPageIndexes("Workflow").Value = "Trans-GAFA-AcctgMasterData"
End If
If oPage.BatchPageIndexes("Type").Value = "HR - HRIS" Then
oPage.BatchPageIndexes("Workflow").Value = "Trans-HRIS"
End If
If oPage.BatchPageIndexes("Type").Value = "HR - Training" Then
oPage.BatchPageIndexes("Workflow").Value = "Trans-Training"
End If
If oPage.BatchPageIndexes("Type").Value = "HRIS - Benefits" Then
oPage.BatchPageIndexes("Workflow").Value = "Trans-Benefits"
End If
If oPage.BatchPageIndexes("Type").Value = "Payroll - HRIS" Then
oPage.BatchPageIndexes("Workflow").Value = "Trans-Payroll-HRIS"
End If
If oPage.BatchPageIndexes("Type").Value = "Payroll - Pay Data Maintenance" Then
oPage.BatchPageIndexes("Workflow").Value = "Trans-Payroll-PayDataMaint"
End If
If oPage.BatchPageIndexes("Type").Value = "Payroll - Pay Data Maintenance - Mandatory Deductions" Then
oPage.BatchPageIndexes("Workflow").Value = "Trans-Payroll-PDM-MandatoryDed"
End If
If oPage.BatchPageIndexes("Type").Value = "Payroll - Pay Processing" Then
oPage.BatchPageIndexes("Workflow").Value = "Trans-Payroll-PayProcessing"
End If
If oPage.BatchPageIndexes("Type").Value = "Finance - Accounting" And oPage.BatchPageIndexes("SubType").Value <> "Accounting Master Data" Or oPage.BatchPageIndexes("SubType").Value <> "Accounting-Payroll Transaction" Or oPage.BatchPageIndexes("SubType").Value <> "Acctg Correspondance" Then
oPage.BatchPageIndexes("Workflow").Value = "Trans-Acctg-Payroll"
End If
If oPage.BatchPageIndexes("Type").Value = "Finance - A/P" And oPage.BatchPageIndexes("SubType").Value <> "Vendor Maintenance" Or oPage.BatchPageIndexes("SubType").Value <> "Payment Processing" Or oPage.BatchPageIndexes("SubType").Value <> "A/P Correspondence" Or oPage.BatchPageIndexes("SubType").Value <> "T&E Vouchers" Then
oPage.BatchPageIndexes("Workflow").Value = "Trans-AP-PaymentProcessing"
End If
' Persist the values to the page
oPage.Persist
Next
End SubThank you
CJ

i've attached a sample of the code.As this is neither SQL nor PLSQL, I'm inclined to say that you're in the wrong forum.

Labels in java

hi
i have a code here where in i have added labels to the JPanel according to the java tutorials
but i cant get to display the labels. i am going nuts.
plz help me
public void actionPerformed (ActionEvent e)
          String item = e.getActionCommand();
          if(item.equals("Close"))
               System.exit(0);
          else if(item.equals("Maintenance"))
               JFrame venMainFrame = new JFrame("Vendor Maintenance");
               JPanel contentpane = new JPanel();
               contentpane.setPreferredSize(new Dimension(765,690));
               venMainFrame.setContentPane(contentpane);
               //contentpane.setBackground(Color.white);
               venMainFrame.setDefaultCloseOperation (JFrame.DISPOSE_ON_CLOSE);
               venMainFrame.pack();
               setvenfrDesign(venMainFrame);
               venMainFrame.setVisible(true);
     } // action Performed ends here
     public void setvenfrDesign(JFrame venMainFrame)
          JLabel label1, label2, label3, label4, label5, label6;
          JPanel panel = new JPanel();
          panel.add(label1);
          label2 = new JLabel("Vendor First Name");
          label3 = new JLabel("Vendor Last Name");
          label4 = new JLabel("Address");
          label5 = new JLabel("Telephone #");
          label6 = new JLabel("Fax");
     } // end of setvenfrDesign

This may or may not be the missing something -its hard to tell with the code, incomplete as it is, though I think you're missing the word or rather the method 'validate()' somewhere in the code, this will update the initialisation of your components.
either at the end of
item.equals("whatever") or setvenframeDesign("blah")

PRAA - How to have multiple payment methods

Hello experts,
We use PRAA/SM35 to create/update employee vendors through a reference vendor. But the payment method is defaulted to direct deposit as in the reference vendor. We have some employees set up for check and every night it is changed back to direct deposit after manually changing it to check. Is there a way we can have two different payment methods for the vendors created through PRAA?
You reply is highly appreciated.
Thanks,
Swetha

Here a suggestion
The idea is to have, in your case, 2 variations of your employee vendor maintenance. You can use herefore the program variants options and have your job adjusted accordingly
Job Employee Vendor maintenance
Step 1 - PRAA - Variant 1 which maps your 'regular' employees for your regular reference vendor (for your regular payment method)
Step 2 - PRAA - Variant 2 which maps your 'exception' employeee for your specific reference vendor (for the non usual payment method)
The question now would be : Is there a way to regroup those employees for which a variation to the payment method is needed : do those employees part of a different company code, employee grouping, payroll area, ... there are various categories (within the extended selected options of PRAA) you can consider and discuss with your HR administration . If this is not a possibility, you can still regroup all those 'exceptions' through their employee numbers
It would be preferable for you to agree with HR to use one of the categorization features ; if this is not an option, you have to consider a process to trigger a change to your program variants (adding the PERNR to the selection option when needed)
PS : Actually Step 1 will be defined for all employees that are NOT of the exception category (exluding those conditions).

Existing Pernr bank details is updated in PRAA program

Hi Guys,
i am changing the existing personal number bank details in PA30 infotype 0005 for these changes will updated vendor master records through PRAA?.
In PRAA if I change the personal details in PA30 will it update the Vendor master records same for address details?
What is the logic behind the PRAA.
Please confirm
Thanks & Regards
K.Gunasekar.
Edited by: Guna Sekar on Feb 5, 2009 12:07 PM
Edited by: Guna Sekar on Feb 5, 2009 3:32 PM

Guna, I expect a typo in your question, the bank details are in infotype 0009 not 0005.
The changes are 'flagged' and will be processed by your next execution of your employee vendor maintenance program (or scheduled job). If the employee has maintained 2 types of bank , It will take into account your current variant preference for bank type (main bank versus travel expense bank).
If your employee does not have a bank defined as per your variant settings, it will take the bank details as per the available bank defined in his current HR record.
HR changes relevant to employee vendor (like address for instance see documentation on PRAA and ALE if applicable) on which HR data (infotype) are considered for your next execution of your vendor maintenance program. This regardless of how the HR changes were caputred / transferred into your FI/AP landscape (direct updae via PA30, PRMD, ESS, LSM, .. or indirect via ALE, EDI, ...) You can also eventually perform a 'mass' maintenance (update execution mode) when you want to apply changes to your reference vendor to your current employee vendors (this will allow all your current employee vendors to reflect your new AP policy like for instance payment terms)

VENDOR_ADD_DATA for custom LFM2 fields

I am looking for a way to use the Vendor Maintenance Program SAPMF02K (XK01/XK02/XK03) to update custom LFM2 fields.
Since there are multiple LFM2 plant(WERKS) Records for a Vendor/Purchasing Org, How can the screen be configured to narrow in on the desired LFM2 record to update?
Goal-Have the additional field appear on the SAPMF02K vendor plant purchasing data screen (330) or as separate button on the alternative data plant screen (341).
Presently I can prompt for the plant and update the existing record, however this is not useful in view mode as the plant field is read only. It also does not look/feel like SAP's XK0x transactions.
Following SAP Note 580266 I was able to use VENDOR_ADD_DATA and VENDOR_ADD_DATA_CS use the custom screen.

Hi jim,
I have a similar requirement.I want to update a custom field in LFM2 table only.I created a screen group and using the badi VENDOR_ADD_DATA and VENDOR_ADD_DATA_CS added my field in the subscreen.But I am able to display the the custom screen tab at screens (0111)General view and Purchasing view(0310,0320) only.I am not able to display the screen tab at LFM2 level (0330).Is there any other BADI or exit TO ADD a custom field in screen 330.Your help will be appreciated.
Thanks,
Naushad.

MM- FI configuration

Dear all,
Can anyone give me the detailed explaination of MM-FI configuration or any links where we get the information about this please
Thanks & Regards
Somashekar Anand

Hi,
SAP Materials Managements
Relationship to Finance
Finance in Logistics
Finance in Logistics - A look from Materials Management
The purpose of this document is to explore the relationship materials management has with accounting in SAP. We will take three swipes at this relationship. First, at an overview level, we will consider a materials management workflow scenario. Next, we will dig deeper as we create documents to support that scenario, and consider the account postings made. Finally, we will consider configuration, and show how SAP automatically posted to various accounts.
A Materials Management Workflow Scenario
Lets consider the following map :
Starting from the top box, we see that a purchase requisition is created. This can be entered manually (as in the case if a secretary wants to order office supplies), or automatically via MRP (through Materials Requirements Planning, where material requirements are generated based on satisfying customer orders, production lines, and other needs). A purchase requisition would contain information about :
1. What is being requisitioned? material / service
2. How much? quantity
3. When is it needed? delivery date
4. Where will it be delivered? plant, storage location
5. How will it be used? item category
6. How will it be paid for? account assignment category - this may also state how the material/service will be used, as the account assignment may be a sales or production order(for example).
A P.Req. may have to go through a release procedure in order to be converted into a purchase order. At this point, suffice it to say that SAP has ensured that employees do not get to acquire materials just because they have nice smiles.
Next, it is up to purchasing to determine a vendor for this requisition. In SAP, the purchasing department has several options : source lists, purchasing info records (material-vendor records), quota arrangements, and vendor master records. A vendor may also be selected based on price quotations attained by the purchasing department.
A purchase order may now be created. Note : in the standard configuration, a purchase requisition is not required in order to create a purchase order. The same information entered in the purchase requisition is entered in a purchase order (note items 1 through 6), plus a purchase order would have a specified vendor.
Purchase order follow-up depends on the purchasing organization. In some organizations, confirmation of a received PO is required. The confirmation could then be a signal to the receiving dock to expect goods on a certain date. Follow-up might include further negotiation, such as price, quantity, or delivery date changes.
A goods receipt for the purchase order is now entered. In the standard configuration, a goods receipt does not require a PO, or any other type of order. With valuated materials, a goods receipt will now cause an account entry. This account entry will typically be against a stock (or production/sales order) account and a clearing account. More about this later. Note that to the side, goods issues and transfer postings are shown. These are also functions of a warehouse, and both can cause account postings. It is important to understand which goods movements will affect accounting and how.
Often an invoice will be received with the goods shipment, but it can be received independently. Invoice verification is the process of determining whether an invoice matches what was received. In SAP, invoices can be entered either from materials management or from the accounts payable side. Most of us would hold that it is up to A/P to enter the invoice, but who better to verify the invoice against the goods shipment and quality than MM? This issue is up to the company and project team installing SAP. The account entries made upon invoice receipt will typically be against the clearing account posted when the goods received and the vendors account (indicating that the vendor should be paid). The invoice may be blocked for payment for various reasons (e.g.invoiced too early, wrong quantity), but even blocked invoices can cause account postings in SAP.
The invoice can now be paid. Invoice payment is done by A/P, outside of MM. This is done by means of payment programs where A/P clerks have the ability to select which vendors to pay, the means of payment, and whether or not to block payment (based on subsequent QI, or poor relations with the vendor). The account postings for payment are typically against the vendors account (signifying that payment is being received) and against cash (or a bank account).
The Documents
The purpose of this section is to show account postings which relate to documents created from materials management. This will include the creation of the following documents :
1. Purchase requisition
2. Purchase order
3. Goods receipt
4. Vendor invoice
Note that RFQs and quotations will not be considered. This is because neither of these documents has an account assignment category. Their only relevance to accounting is that they specify a material (and thus a material type), and the quotation specifies a vendor and a price. With no account assignment category, however, there is no specification as to who will pay for the ultimate purchase.
The purchase requisition
The purchase requisition is created through transaction ME51 (Log > MM > Purch > Req. > Create). As mentioned, the following are determined in a purchase requisition :
1. What is being requisitioned? material / service
2. How much? quantity
3. When is it needed? delivery date
4. Where will it be delivered? plant, storage location
5. How will it be used? item category
6. How will it be paid for? account assignment category - this may also state how the material/service will be used, as the account assignment may be a sales or production order(for example).
This is shown on the following screen :
As mentioned, neither the vendor, nor the material price is specified in the requisition. A vendor can be specified in a requisition which has been "allocated", but thats a separate story.
The purchase requisition has no direct account postings. When a purchase order is created with reference to the requisition, the account assignment (category) and the material items are carried over. As of 2.2, the account assignment can be changed when the requisition is converted to a PO, but not the account assignment category. (You can change the account assignment from one cost center to another, but not from a cost center to a sales order -- different account assignment categories).
The purchase order
A purchase order can be created for a known vendor with the transaction code ME21 (accessed by Log>MM>Purchasing>Purchase Order>Create>Vendor known). An un-allocated (no vendor previously selected) purchase requisition might then be referenced. Alternatively, a purchase order can be created with reference to an allocated requisition using transaction code ME58 (Log>MM>Purchasing>Purchase Order>Create>via requisition).
As mentioned, the purchase order has the same entries as a requisition, plus item prices and a specified vendor. A sample purchase order is shown :
The purchase order has no direct account postings. However, account postings from goods receipts and invoices made against POs are very much affected by accounts designated in the POs. As of 2.2, a purchase orders account assignment can be changed as long as no goods have been received against the PO, and no invoice has been posted against it. (Thus, if no GR or invoice has been posted against a PO, the account assignment can be changed from one cost center to another, but not from a cost center to a sales order -- just like with requisitions).
The goods receipt (for a purchase order)
A goods receipt for a purchase order is created using transaction code MB01 (Log> MM>Inventory Management>Goods movement>Goods receipt>For purchase order). A movement type can then be selected via the menu bar, or using the list of possible entries. In SAP, every goods movement has a "movement type". The three headings of goods movements in SAP are good receipts, goods issues and transfer postings. Most goods movements will cause account postings. More will be said about that later.
With every goods movement (or transfer posting) in SAP, a material document is created. For every goods movement which affects a G/L account, an accounting document will be created (separate, but tied, to the material document). Material documents are not deleted, but they can be canceled or reversed. Thus, if a good receipt was posted with the wrong storage location and the wrong quantity, the receipt could be canceled. The cancellation will create a new material document (and probably an accounting document which will contain reverse debit/credit entries to what were entered in the first accounting document). Note, that if a goods receipt is entered for twenty-five pieces of a material, and only twenty pieces were actually received, a reversal could be entered. This reversal would be for five pieces. It would also have a material document, and the associated accounting document would have reverse debit/credit postings for the value of the five easy pieces.
The following is a goods receipt for the purchase order created in the last picture :
The movement type is one of the most important entries in materials management. It controls how account postings are made (as we will see), and it is very easy to overlook, as it is only a three-digit identifier. After several materials movements, one becomes familiar with common movement types (e.g. 101 - goods receipt of a PO, 201 - goods issue for a sales order, 561 - initial stock entry, and so on). The movement type will control the account postings with the aid of other parameters (such as the material type and the account assignment category).
The accounting view of the above transaction is shown in the following view :
Using the movement type (101), SAPs automatic account assignment was able to determine that a debit should be made to the cost centers account (which was specified on the purchase order), and the GR/IR clearing account should be credited. With automatic account assignment, the proper accounts with their respective "posting keys" were specified. Posting keys determine whether debits or credits are made against given accounts. More will be said about posting keys later.
The invoice (for a purchase order)
Invoices on the materials management side of SAP are entered via transaction code MRHR (Log>MM>Invoice verification>Document entry>Enter invoice). One could also enter credit memos in materials management (via a similar path to that just shown), as well as subsequent debits/credits against previous entries. As mentioned, these are usually entries made by accounts payable (A/P) clerks, but SAP allows its customers the option of entering this information in MM.
In SAP, invoices are not posted unless total debits and credits balance. New in 2.2, preliminary posted invoices can be made for invoices. In such a case, the proper PO to register the invoice against is unknown, therefore an A/P clerk can enter the invoice information, and "park" the document. Note that in "parked" invoices, no account postings are made.
Invoices can be blocked for payment because tolerances are exceeded. For example, the invoice date is much before the expected receiving date stated on a PO, thus date tolerance has been violated (it wouldnt be the first time a date was violated). Similarly, an invoice can be entered for a quantity greater than that which was received. Here the quantity tolerance has been violated. In SAP, even though an invoice is blocked for payment, account postings are made.
With goods movements, a material document is always created, and an associated accounting document is created when G/L accounts are affected. With invoices, one accounting document is created. An itemized listing of an invoice entered with reference to the PO created for this document is shown :
The accounts referenced in the above picture are not posted to until the invoice document has been saved. The "accounting view" of the above saved document is shown :
The accounting view of the invoice reflects what the item view showed, but note that the account entries could not be made unless the invoice balanced.
Also shown in the picture are tax codes. Tax codes can be created with a simple valuated entry (which would be manually maintained by A/P, purchasing, and system administrators). Tax codes can also be maintained via an external interface. In the US, tax codes are defined by :
1. the jurisdictional laws of the place to which the goods are shipped,
2. the material type of the goods being shipped, and
3. the taxability of the entity (customer) receiving the goods.
There are more than 50,000 different tax jurisdiction areas in the US (as they are defined by state, county, city, zip codes, etc.). External tax systems (such as AVP or Vertex) maintain the taxation rates for these jurisdictional areas. In 2.2, modifications have been created to interface external tax systems. In 3.0, this interface will be standard.
The account entries described in this section are shown in the following "T" account entries.
With the goods receipt, the debit to the cost center account (which could be the cost centers stock account) represents an increase in on-hand stock, while the credit to the GR/IR clearing account represents an outstanding invoice approval process.
With the invoice receipt, the invoice is verified that, in fact, the goods were received, and were of acceptable quality. This invoice entry creates a debit to the GR/IR clearing account (to balance the account), and a credit to the vendor account. A credit to vendor account signifies that in order to make the account balance, the vendor must be paid (debit the vendor account). Note that if the received goods were of sub-standard quality, payment could be blocked at this point by either not entering the invoice, or (more likely), the invoice would be entered, but blocked for payment. (Invoice verification is considered the third link of "three-way matching" -- the matching of the PO, GR and invoice. The invoice verifies the purchase order price and specifications, and that the goods in the PO were received and of appropriate quality)
The payment of the invoice is the final link in the workflow chain. The vendor is paid (account debited), and cash is decreased (credited). In SAP, maintenance of vendor payment is outside of materials management, but with an integrated system, it is coordinated.
Automatic Account Assignments in Materials Management
Consideration of automatic account assignments in MM will be approached in two steps, according to the accounting documents created in the last section. First, we will pursue the account postings made by goods movements, then we will consider account postings made by invoice entries.
Account postings through goods movements
Lets start from the basics. As mentioned, with each goods movement there can be an associated account posting. Where are these account postings maintained? A good place to first look is table 156s. This is accessed by table maintenance (SM31), entering "T156S", and hitting either the "Maintain" or "Display" button. The following table is then presented :
This table shows configuration information based on all the movement types (hundreds) in SAP. For our discussion on account postings, we do not need to concern ourselves now about the entries in the column and to the right of "SLoc".
From the fields shown, a quantity string and value string are determined. Note, that it is the combination of all the appropriate fields which makes this determination. The quantity string determines which quantity fields are updated (through a sequence of instructions), and the value string determines which account posting keys will be signaled (also through a sequence of instructions). Therefore, in order to determine which quantity string and value string are to be referenced for each goods movement, the significant fields of table 156S are now defined from left to right, the following fields have the following meaning :
Movement type - the three digit code associated with a goods movement. It must be specified with every goods movement.
Value update indicator - every material type is designated as to whether or not the material value is updated during goods movements. Thus, the value update indicator signifies if the account posting can affect the material account.
Quantity update indicator - every material type is also designated as to whether or not material quantities are to be updated during goods movements. Note that the the material types quantity update indicator and value update indicator must match a line entry in order to use the associated quantity and value strings.
Special stock indicator - this field indicates who owns the material and who gets the material. For example, the indicator might be blank (" "), where the stock is taken by the user in their plant. The indicator might be "K" (for consignment), where the vendor owns the material, but the stock is taken into the users plant.
Movement indicator - This specifies the type of order the goods movement might be against. For example, the movement could be with reference to a purchase order, a delivery note, or with no reference.
Receipt indicator - This field is currently not used. In the future, it is expected that specification will be possible to determine if this movement was for a stock transport order or an outside purchase order
Consumption posting indicator - this field is used in the case of goods receipts for purchase orders, and is defined from the account assignment category in the PO. Thus, in our previous example, the account assignment of "K" (for cost center) in the purchase order ensured that the receipt debited the cost centers account, and not the stock account.
So with the right combination of these seven (actually six) entries, we determine quantity and value strings. The quantity string is handled very similarly to the value string. Quantity strings are maintained in table 156M (accessed via SM31 and display/maintain "T156M"). In the last picture, the quantity string for the top entry is ME02. In table 156M, the quantity string indicates if orders are to be updated and other relevant quantity information. This table will not be analyzed here.
Value strings are handled in table 156W (accessed via SM31 with display/maintain "T156W"). The value string for the top entry in the last picture was WE06. Table 156W is shown :
The value string WE06 has two entries. These entries have different transaction/event keys (also called account keys). The transaction/event (t/e) keys specify the type of account to be posted to. These transaction/event keys are found in table 030. Thus, WE06 specifies that t/e key KBS will be referenced first, followed by key WRX. Lets look at table 030 (accessed through SM31, display/maintain "T030", and select group RMK; OR via the menu path Tools > Cust. > Config > Acc. > Fin. Acc. > Book. > Bus. trans. > Gen. Ledger > MM > Auto posting).
Paging down through this table we see that KBS signifies an account specified in a purchase order, and WRX signifies a GR/IR clearing account. If we double-click on (or choose) KBS, we are brought to the following screen :
So how do we know which posting key to take? Is this a debit or a credit? We look to table 156 (a.k.a. "T156) in SM31.
For movement type 101, we see that the first entry is "S" under D/C. This signifies that the first entry is to be a debit, thus the first t/e key (KBS in this case) is a debit. Therefore, we look to posting key 81.
Note the line "posting keys are independent of chart of accounts" in the screen for key KBS. Lets look at where posting keys are configured in transaction OB41 (in table TBSL through SM31, or via the menu path Tools > Cust > Config > Acc > Fin Acctg > Book > Bus trans > G/L > Control > Posting keys).
Posting key 81 shows a debit to a G/L account. Lets look into this...(double-click or choose posting key 81)
We see that this key causes a debit to the specified G/L account. Thus, an account was specified in the PO (since 101 was a GR for a PO), and by finding the value string in table 156S, then the appropriate transaction/event keys in table 156W, and then by digging into the t/e keys in table 030, we were able to determine the appropriate account postings. So that told us about the debit made, but what about WRX? Lets also look inside t/e key WRX in table 030 (we first must specify the chart of accounts, in this case CAUS) :
Here we see different postings, a valuation grouping code, an account modifier and a valuation class. Since the account modifier is not shown in this screen, well cross that bridge when we get to it. For now, lets look into the valuation grouping code. This is found in table 001K through SM31 (also available in transaction OMWD; Tools > Cust > Config > Log > MM > Val/Acc.assign > Config > Acct. det. > Val. area grouping).
.From this screen, we see that the valuation grouping code is used to group different valuation areas and/or different company codes together within a chart of accounts so that they have similar postings. So we understand the valuation grouping code, now how about that valuation class? Thats attained from the accounting view of the material master (for that specific valuation area).
For this material, the valuation class of 3000 is chosen. When this field is drilled into, we see that for this raw material, the system knew that only certain valuation classes were allowed. How did the system know which valuation classes were allowed for this material? It knew because when this material was created, a material type was chosen. Now on to material type configuration. This can be accessed via transaction code OMS2 (T>C>C>L>MM>Master data > material > control data > material type > click on change or display), select "ROH" (for raw materials), then click on the "account assignment" button. This shows the possible valuation classes assigned to the material types.
So for this raw material, the valuation class chosen was 3000. Therefore, back in table 030, for the t/e key WRX, using the valuation grouping code found in table 001K and the valuation class for the material (found in the material master), we can determine the GR/IR clearing account entry.
While were in the material type screen, lets look at one other thing -- quantity/value updating. From the last picture, click on the button labeled "quantity/value". The following screen appears :
Note that to restrict quantity or value updating of this material type, the button "in no valuation area" under the headings of quantity or value updating would be selected. Thus, FOR EACH MATERIAL TYPE, THIS IS WHERE WE DETERMINE IF THERE IS QUANTITY OR VALUE UPDATING.
Back to our example from II.3 (a goods receipt for a purchase order)
So guess what! With what weve covered in this section were ready to track down how our goods receipt posting in the last section happened as it did! Lets consider what we know about the goods movement :
1. It is a goods receipt for a PO -- movement type 101.
2. The PO had an account assignment category of "K", for a cost center and therefore is an item set for consumption.
3. The material used was a raw material with a valuation class of 3000.
4. For raw materials, there is both quantity and value updating.
5. It is "standard stock" item (no special stock type)
So lets look to table 156S ==>
We are looking for the entry which is the third from the top. It meets all the criteria. Therefore, we are looking to value string WE06 for answers WE06 is found in table 156W.
As we said about this screen, WE06 has only two t/e keys. We determined the account posting for KBS in the following way :
1. We found KBS in table 030
2. Under KBS, we saw that two posting keys were there, one for a debit, one for a credit
3. In table 156, we found that the first entry is a debit, thus we select posting key 81
4. Next we looked to table TBSL (in transaction code OB41), and chose posting key 81
5. There we saw that posting key 81 causes a debit to a prespecified G/L account (the cost center account specified on the purchase order)
We also determined the account posting for WRX in the following way :
1. We found WRX in table 030
2. Under WRX, we saw that we saw that we needed to specify a valuation grouping code and a valuation class in order to determine the proper GR/IR clearing account.
3. In table 001K, we saw that for our valuation area (US01) and our company code (US01), we have the valuation grouping code US01.
4. From the accounting view of our material master, we saw that our material has a valuation class of 3000 for the plant we are operating in (US01).
Therefore, in table 030, with a valuation grouping code of US01 and a valuation class of 3000, we have the GR/IR clearing account as account number 191100. This is shown in the accounting document created for the goods receipt.
A small change to the purchase order...
We said that a purchase order creates no direct account postings. However, they very much affect account postings for subsequent documents! In the purchase order of section II.2, what if we had chosen the account assignment category as being standard? Lets look again at table 156S.
In this case, we choose the top entry -- goods receipt for a PO, where there is no consumption specified. We are thus given the value string WE01. Lets look to table 156W.
Here we have 12 different posting keys! Note that there should always be more than one posting key for a goods movement because there should always be at least one debit and at least one credit. We saw that for movement type 101 (in table 156), the first entry is a debit. Thus, lets look to table 030 to see what a debit under posting key BSX does.
Again we see the valuation grouping code US01 and valuation class 3000, we have account 300000. This is exactly what we find with this goods receipt ==>
Offsetting entries for inventory postings (Key GBB)
One last point about automatic account assignments from materials movements.
One of the t/e keys definable for a value string is GBB. This is a key often associated with goods issues, but can be used whenever offsets are required for inventory. This key is maintained in table 156X, which is shown :
As we determined the quantity and value strings from table 156S, here we not only can find the value string, but also the account modifier. If we look in table 030, we see the t/e key GBB. When we choose that key, we find the following view :
Where in the t/e key screens of BSX and WRX we only had to know the valuation grouping code and the valuation class, here we also need the account modifier. This screen shows that a goods movement which has a valuation grouping code of US01, a valuation class of 7900 (commonly used for semi-finished goods), and an account modifier of AUF would have debit and credit postings made to account 895000.
An Easier Way...
To review, we recommend a way of determining account postings from goods movement documents :
1. Check table T156S for the appropriate movement type
2. Find the appropriate movement type and value string in table T156S based on :
a. if the material type is quantity and/or value updated
b. if the item has a special stock type
c. what type of movement is occurring
d. what type of account assignment the item might have (consumption, sales order,
e. stock account, etc.)
3. Based on the value string, check table T156W for the sequence of t/e keys accessed
4. Check table T156 to determine if the sequence from T156W begins with a debit or a credit
5. Check table 030 to see the possible postings for each of the t/e keys
a. for the t/e keys which have simple entries of posting keys (as with KBS), look to table TBSL to see what account this posting key affects
b. for the t/e keys which have a valuation grouping code, account modifier, and a valuation class specification, find the account by the following :
look to table 001K to find the valuation grouping code based on the appropriate valuation area and company code
look to table T156X if an account modifier must be checked
look to the accounting view in the material master to find the appropriate valuation class
To check the account postings, use transaction code OMWB (accessed via the path Tools > Cust > Config > Log > MM > Val/Acc.assign > Config > Acct determ > Auto posting > Simulate). Hit cancel (in 2.2) to get to the next screen, then hit the "Simulation" button choose a plant, material and a movement type, and hit the "Account assignment" button.
This is one way to check the configuration without creating all of the documents.
Postings from invoices
Account postings made by invoices are much easier to understand, but harder to examine, than goods movement account postings. With invoices and credit memos, there is an associated document type (note the initial screen of an invoice)
However, we can look at the posting keys for invoices we can expect to be affected. These are maintained with transaction code (accessed via the path : Tools > Cust > Config > Acctg > Fin Acctg > Book > Bus trans > Base params > Control > Posting keys). We are brought to the following screen :
We see that posting key 31 is an invoice in which we credit a vendor. Lets choose this key (or double-click on it).
We see that this is a credit to a vendor account. We also see that posting key 31 has a reverse posting key of 22. The previous screen showed that this is a reverse invoice receipt (different from a credit memo). A note about vendors -- in purchasing, vendors can be created with regard to purchasing, or centrally. If a vendor is created with regard to purchasing only, the vendor will not have accounting information maintained. Thus, the vendor would not bill in the SAP system. This is not to say that the vendor will not bill (we should be so lucky), just that it is not done in the SAP system. This might be for SAP users who are using an external system for accounting (or A/P only).
When a vendor is created, it is designated with an account group. The main functions of a vendor account group are :
1. to designate if the vendor is a one-time vendor
2. to specify the number range the vendor might be assigned to (to assign a vendor name)
3. to maintain screen control for vendor maintenance
Vendor account groups are maintained in transaction OBD3 (Tools > Cust > Config > Acctg > FI Acctg > Book > Master Recs > A/P > Control > Acct groups). If we choose LIFA (general vendors), we see the following :
The screen shows that the number range for LIFA is "XX" (transaction XKN1 shows this to signify external number assignment). The screen also shows that this is not a one-time vendor. If we double click on "Company code data", and double-click on "account management" in the next screen, we see how accounting fields for this vendor are maintained in the vendor master record.
If an invoice is created with reference to a purchase order, the account postings are already specified, as checking is done as to whether the goods have been received. Note that in creating an invoice, it is not necessary that an A/P clerk reference a PO (although it is advisable if known). If a PO is not reference, the A/P clerk must manually maintain account entries. These account entries have associated posting keys. For example, a freight charge might have a posting key of 50. This account can be seen in table 030. Likewise, unplanned delivery costs can be charged against the group receiving the goods.
During invoice entry, alternative account entries can be entered, either as debits or credits. Thus, account determination is made as the invoice is entered.
Postings from purchasing documents
One last note...
You may find that some account postings happen when referencing purchasing documents, and there is no reference to these postings in table T156S. For example, freight charges. They can be specified in a PO, but how does a goods receipt know to take the POs freight charge over to the account posting?
First, lets remember where freight postings are made in a purchase order. In the pricing condition record (note a special condition type) :
So the condition record of the screen shown has a condition type of FRA1, a percentage freight charge. Purchasing condition types are tied to account postings through PURCHASING configuration. Thus if we look into transaction M/08, yes with a "/" (Tools > Cust. > Config > Log > MM > Purch. > Functs. > Conds. > Pricing > Pricing Proc. > Pricing Proc.), we see the following screen :
If we now double-click on RM0000 (the first pricing procedure), page down to find FRA1, hit the "change view" button, we find the following screen :
Here we see that condition type FRA1 is tied to account key FR1. If we now look in table T030, double-click on "RMK" (MM postings), and double-click on FR1, we see that (in CAUS, for example), these freight postings are made to account number 192100.
Regards,
Archit

IBAN missing in CREMDM & CREMAS

Hi,
I'm trying to send Vendor IBAN (International Bank Account Number) field to ECC V6 via XI using CREMDM IDOC structure but I noticed IBAN segment/field is missing in CREMDM and CREMAS idocs, even though I can enter vendor IBAN via vendor maintenance transaction XK01/XK02. Anyone know how I can add IBAN to the idocs w/ least amount of custom development?
Thanks,
Susan

Hello Susan,
please check the SAP help to IBAN:
http://help.sap.com/saphelp_erp2005/helpdata/en/45/c28b18ccc247f3e10000000a114a6b/frameset.htm
I had the same problem in a Masterdata Project more than 2 years ago. I remember that we chose to leave the IBAN Code to be manually generated in each system.
As far as I can remember, the problem was not to extend the CREMAS structure and send the IBAN Code, but to override the system checks by the Idoc processing in the client systems.
The problem is not only of technical nature, I think you shoudn't override the system checks, out of good reasons (audit?). Of this I am not sure.
If you do choose to send IBAN data, please let me know how you did it.
Thanks!
Best Regards,
Mircea

Vendor maintenance

Similar Messages

Maybe you are looking for