You are on page 1of 37
THE SIMPLIFICATION OF THE VENDOR MASTER IN S/4 CONTENTS CONTENTS Contents 2 ‘The implication of the Vendor Master Record ef Supplior Mastor Dita in $/4 HANK a Vendor Account Groups A ‘upper Number Range s ‘Creatingthe Supplier Master Data 10 Maietaining the Supplier Record 15 LUn-simpliying the Suppl Recon 38 (One-Time Vendor. a Vendor subrarge. 23 Tables 24 Migration, 35 summary 2 waro,poserrc A THE SIMPLIFICATION OF THE VENDOR MASTER RECORD ‘As of SAP 5/4 HANA on-premise edition 1511 the use cf Vendor (and Customer] Master records in SAP is now outdated, Recont SAP dovolopment: have ured Business Parnas to store master data, The Businass Partnor ic now capable of maragig tho maiterdata fr busitoss partnor, customars and vordovs. fe ‘such the Vender master record isnow obsobtein /4 HANA, the mandatory aporoachis touse the Business Partner approach (Customer Vendor Integraton (CV) ands refertedtoas the Supper. ‘Only SAP Business Suite austere using C/V integaten can move to SPP S/4 HANA, on premise edition 13511 using the conversion aporoach. tb recommended, but nat mandaton that Busiess Partner IDand Cuctamer-b/VendorI0 aa the came. tis important to note n tho caceof avelapping Customer and ‘Vendor number ranges in SAP Busines Suite then addtional number range alnmmentuil be requires Ieleimportantto note thatthe Business Partner Approach It not mandatory fr SAP Simple France, on ‘reise edtion 1503. Transaction BPs nowthesingle port of entry tocreate, edit andisolay master data for vendor (along vith cuscomersand business partners) Trarsactions NOL, MKO2, MKO3, FEO, FKO2,FKO3, KOI, X02 and XKOS ate no longer avalable and redirect Wo Wansacton BP. AE ths current Line there f no ably Lo ‘mass update the Vendor roughkK99, a mass update transaction son the realmap for 2futureSAP 5/4 HANA release. SUPPLIER MASTER DATA IN S/4 HANA ‘The supplier master datais stil structured inthe seme way n5/4HANAon premise edtion 1511 as the ‘SAP Busnes Sulte: general data, accourting data and purchasing data, What has changedis 2 Business Partner Roles now used torepreserteachof thes views General Data ‘The generalinforration about the supplier, such as name, search terms, adress, telephone, and fax ‘This data can be ertere using BP Role 000000 Business Partrer (General). Thisinfermation could be ‘entareaby the group resgonsblefor creation of vendor records Furthe! dara relatngto accounting ane purchasig can subsequently be aed. waro,poserrc A Pecounting Data ‘Accountingdataishelé a thecompeny code level stil Ths data ncludes tac information, bank detals, recondition accounts, payrenttenns and paynent methods. This infermation is elé agaist BP role R.VNOOFI Wencor. Purchasing Data ‘The purchasing data is entered forthe vendor ata purchasing organization vd. This dataincudes ‘contol data for purchasing, partrer‘unctons an default pufchasing Ns, The inormaton s enterea sing BP role FLV Supple. VENDOR ACCOUNT GROUPS Vondorsare stil exegoriaed through a group, tho groups n S/4 HANIA on promée editon 1511 10 restricted naw to (PD One Tine Supoler, EMPL Employee and SUPL Supplier. These acount groups are sill defined va the navigation path IM> Francal Accounting > Accounts Recelvabe & Accounts Payable > Vendor Accounts > Master Data> Preparations for Creating Vendor Master Data > Define Account Groups vith Screen Layout (Venders). Change View “Vendor Account Groups”: Overview FE neers TORRGS Vendor Account Grups Group Name o ero rete super oO MPL Employee as Suppier hd SUP Supple: The Business Partner Group ks mepped backtothe Verdot Master Account thrcugh the menupath ross ‘pplication Componerts > Master Data Smcironisatio > Customer/Nendorintegraon > Settings for ‘Vendor Integration > Feld Assignment for Vendor Integration > Asign Keys? Define Number Assignment {for drection BPto Vendor. In his 5 th grouping you choose forthe ruber range assignment ofthe Business Partner determines F ths record relatos to a One Time Supplies, an Employee as a Supplier ora ‘Supplierin ts treatment as aSupoliorinLogitis, nao ose wano,poserrc AE ‘The field status contr! now takes pice at the Business Partner levelin the main Inthe delivered settings the Vendor Account Groups have tho felis set as "Optienal Entry" a none | 900009000000000000008 Doe 900000 po Ooo Oo Doo, © ® ° 2 ° Inthe Business Parmer coniuration you deine the requied, optional er suppressed dats fr each Buses: Role. The datafiel are grouped hn "éatases”in/é HANA on premie edition 151, sar to the fed groupsinhe SAF Business Suite. The configuration sreen lows you to hie (Hie) certain fel, rake felis mandatory (Regent cr optional Opt entry, 0° slay CApay only. Fis ‘connigution becomes spcticto the Business Pare! Roe that entered when the vencor deta are waro,roserrc A ‘ceated. The navigation path & ING> Cross Applcation Components > SAP Business Partner > Business ‘Partner > Basie Settings > Field Groupings > Coniigure Fld Settings per BP Role ‘The screen layout canalo be modified for 2 particular activity se the options presented when entering ‘the venéor detale may be diferent from when changing the vendor data. The navigation path or this & row alo uriar the Business Partner configueat on IMG> Cros Appleation Components >SAP Buiness Partner > Business Partner> Basie Settings > Feld Groupings >Corfgure Feld Atrbutes per Ativiy wano,poserrc A SUPPLIER NUMBER RANGE ‘The conigwation forthe number rangeassgnment has alo moved fromthe Vendor tothe Business Partnar configuration. The delivered SAP cetingshaveall the Verdot Accounts ascignad tothe number range BP: PORES penton jMmoecrange | OY i ete Suk ¥ + ‘rooyes Suter a . [see Sone ” | BP ic anexternal number range, ss the numbers passed from the Business Partner tothe vendor table LEAS LIPNR, (Beafrom no To Number sate «| Oo 1 Feacoaco coosssse ° oO rcoaerocooe cnoes993 ° oO [a eaocaocoos mam ° @ | gee sosacenne soeesoee ° oO a mam ° 2 Just ikethe Vendor Settings inthe SAP Business Sulte, the number ranges aisigedto the Business Partner in 5/4 HAN on premise eaiton 1511 can be extemaly or ntemaly assigned, Often adecsion i ‘made tocreateaifierent ruirberrargesfor each acount greup or tusiness partner role, This regules ‘careful consideration whea definng number ranges toprevert number ranges fem overlappng. “The navigation path tocreate Business Partner nuribe ranges is IMG > SAP Busines Partner > Basle ‘Settings > Number Rarges and Groupings > Define Nurrber Ranges waro,poserrc A ‘After the numbar range is define. its signed toa grouping The reviation path is WAS> SAP Business Partner > Basic Settings > Number Ranges ard Groupings > Define Groupings and Assign Number Ranges. rat rarer neg (ow. 9b eaten sanded ve 62 ‘exwralunercnurbeng (how 03 exwalathaumee rumbung AB earl trbung or Sikyes EE [eceralapra-umee 5D ahs 8 wewmtraroung'or@o ws oe ‘The groupings are selectable n tansaction BP when creating your vendor data record, and inthis way the esivad number ranges wes. wano oscar c AE ‘The Business Partner can havea rultfacsted relationship withthe Customer, that represented through ‘multiple Ausiess Partner Roles. Inthe cate tis obsolete tothink ofa singe, cefned number rangato a single ‘Account Group to Identify the role or purpose ofthe Supplier. CREATING THE SUPPLIER MASTER DATA ‘As mentionad earl, the:rarsactions wed in SAP Business Suiteto create the Vendor Master Record (0K01 Create Vendor Centrally, FIO1 Create Vendor via Accounting, and MKD Creste Vendor via Purchasig) no longer exis in SAP /4 HANA on premise edition 1511. Transaction BP is now the central poin' tocreate, change or display the Business Partner recor that represents the Vendor. Atthispoint ‘he vattonal Vendor create transaction redirct tp transaction BP, butthistransaction has nat relly been integrated in the Logists menu at this point. This tansacton can be found using the navigation path SAP Menu> Logistics Settlement Management > Environment» Master Data> Mainvain Business Partner. ‘The Bisness Partner canbe created as a Person, Organisation or Group. The selection conras addtional ‘dara that canbe held against the Business Partne, fr a person this includes academic qualifications, ‘occupation, martal status, et. Fran organization you can malntan a type of nd ‘The organization thats being crented can be asigned multipe Business Partner roes. The robs behave similar tothe olaverdor Account Group, cctating Nd control andat wt organization level (Compary Code or Purchasing Organsavon fer example) datacan be hel at. Utimately ese conuls wil define nao ose how the Business Partner record can be utilzed, The number range assignment in §/4 HANA on premise ‘dion 2811 is differant fromthe SA? Businoes Suto, the desired number rnge grouping i clocrodfrom ‘the drop down when entering the data Inthis cae we create a Business Partner (General) (B8POLD) to log a posible source of supply. This business partner role contans data jst atthe general evel ~adaress deals, contact infomation, ec. Bankdetailscan alo be entered at thi time, oradded at later cate ‘When cresting a record of Business Partner (General) ype, no entry's made inthe Vendor table LFAL. At ‘tis point, with just General dats; the system has not Hertfed relationship with thi Business Partner aca ‘Supple. ‘After the Vendor has been approvedor quafied for use, the purchasing detallscan be addedto the record by asigning the Business Partner Role Supplier (FLYNO1) to the record. While displaying the existing Business Partrer Record in edit mode, select the Supplier Business Fartner Role from the drop ‘down, The general data that has areaay been entered aganst the Business Parner (General) oles ‘copied in tothe new role and can beuptated or changed trom here. {shouldbe noted thatthe field control corfigyation i at Business Partner Roe level this case the data coped from the Business Partner (General) address dtals nay not satisfy the required fields stipulated inthe Supller BP Rol. Adltonal general level data may need tobe added before the new BP. role can be saved. You willabo see on the tool bar thatan option now exststo Hold data at “Purchasing” level. By selecting ‘his option you can enter the required Purchasing Organisation level daa nao ose ‘You speci the Purchasing Organisation level at wich youwish to enter the daca, The data held at this level deat purchasing information, LogistesInveice Verification data and Partne Function b the same «the Purchasing Orgensation data thatwae held agahstthe SAP Busines Suite Vendor Master Account, waro,poserrc ‘supplier may deal wth multiple purchasing departments ofa single company, negotiations may be limited toa specific geographical regon for example. Te purdasingterns a Vendor cffers inthe United ‘States may ater great trom thase offered n Bras the BP role hols the purchasing data at Purchasing Organisation level, ts posible o holdiferent gurchasng data fo the same Supplier in ‘each Purchasing Orgaristion. ‘When creating a Business Partner to represent a Plant as Supple for Inter company er Stock transport ‘order processing iti Important to note thatthe Plant asigrment is onthe General Data. The tab Supplier: General Data contain a section on Additional Geral Data ichere that you desgrate the Plart thats ‘represented by the suppler. This field updates LFA1-WERKS. In SAP Business Sutte, this designation was, performed in the Additional Purchasing Data. ‘A this point the Business artnercan be used for purchasing transactions ~RFs processing, ceationof ‘contracts, eventhe rating a Purchase Order, However, jut like the Vendor Master Account in AP Business Sut, theSuppler needs to have Accounting data entered at the Company Code level tallow payment to be made. instead of using transaction FKO!, te Business Partner role Hl Vendor (FLVNOO) ‘You willsee with this 8 role, youhave te option of accountng information atthe Company Cove level nao ose ‘The Vendor OP rele in/4 Hans on premise edtion 2612 stores the same accounting information that ‘you would enter into the Company Code section ofthe Vendor Master Recon in SAP Busnes Suite. Its possbleto define vasty different Acounting data across multiple Comeany Codesfor the BP ole wano,poserrc Stee ee Sef. eer MAINTAINING THE SUPPLIER RECORD. ‘As has been mentioned, transaction BP snow the central pont cf acces forthe creation, maintenance ‘2nd displaying of Supplier dota. The general data can be mainained in any ef the business partnerles, and thiswillreplieae acres al the Busivoze Partner rlecdofin Fo the supple. ‘There are no longer defined vansaction for the blockhg ofthe supplier, orflagging the supplier for eletion A iab include that allows you to fag fer deletion or bloc the B roe drealy in transaction BP. tryou ws 1 Nag for deletion or block a Supplier for aspect Purchasitg Organisation, you Nees to select the Supplier BP ole, you wil then be presented withthe necessary tab f you wsh to fag for ‘eletion(blocka Suppler for «specif Company Codethen you select the Fl Vender BP ral. ‘At the general data lve, there sno deletion fg, An indicator exists to identify the record is valié for “chiving. IF during thearciving run the system find cpen transactions or a Supple lagged as relevant {orarchiving, the arching indicators igored. A cental block can be applied ac general dataleve, preventing wrtanacttiesfrombeing executed, waro oscar c Toalowtime dependent changes to the Business Partner, you must activate the functions in the ‘olloning menupath WAG > Cress Application Comgonents> SAP Busines Partner > Activation switch for ‘As youcansee inthe functors lcted its posible to make a date valid changet the Bushes: Porter ‘addrase,and bank deta, Uniortunaraly at thistime no function aictsto make data dapandent changes tothe Purchasing Organisation of CompanyCode data for example, payment ters) waro oscar A You latallrequrecaddreses inthe address overvewtabof the Susiness Partner. Usethe create icon (B) toads the necessiry addresses (Ale oetoe witton juldte oe ED ‘You can then select the appropriate address designation, and click on the create icon (jn this section toadtvate the alternaive adéres. You wil be required to stipulate the valty period for thisalternative asses. etiod for Adéoss Ung ald From val To 199) oun |Adées bescroton val om Yad To |_ [cA _ changed street / ferent town ONNSY 482 06.10.2016 31.12.0999 wano,poserrc A You can now see the diferent adireises that ate maintained fer each function, an the valid period for thi addrore usa. TR en aes opt en eine er ‘You are not alowed to restict the vllty ofthe standard address ofthe Business Partner even when function BUTO20Is act. UN-SIMPLIFVING THE SUPPLIER RECORD Itis possible tocreate your own Business Partner Roles in /& HANA on premise edition. In ths casethen you can create a fale that mirorsthe Vendor Master Facord from SAP Business Sute, allowing you to sore Purchasing data atthe Purchasing Organisation level, andthe Accountng data at the Company Code level on the sare B? rol. The navigation path to define a rew Business Partner role is NG Cross ‘Poplcaton Componerts > SAP Business Partner > Busines Partner > Basic Settings > Business Farmer Foles> Define BP Roles BP role 2FLVNX~ External Supplier has been addedhere, the description here Business Partner Vendor (Company Code & Purchase Crg Data) reflects towwe are combining thase two datasets into the one OP cle. waro,poserrc A ‘The dtals screen for the BP Role Category allows youto define where this BP rolecan be used ~isitan Organisation, aPerson, a Group or acombiration, waro,oserrc A ‘The BP Role Grouping establishes the data ews thatthe BP role corti. You canassign he required BP foe groupirg tothe rew BP ole though the follows naviesticn path IM> Cross Appcation | ‘Components > SAP Business Parte > Busines arter > Bsc Setings> Business ParterRoles> Dene BP Rle Groupings. ‘The 8 role grouping bs defined with thesame identifier as the BP role that was created ZFLVINK, ‘Dabgsmcue | nse cousmy ‘(RE Be rae ove —— ‘We thenassignthe two BP roles FLVNOO— fl Vendor, forthe Accounting data tebe het at Company (Code level; andFLNO1 ~ Supple, for the Purchasing data tobe hel at Purchasing Organisation level, waro,poserrc EE BRIBE Kole Groupng fl Intransicton BP, when selec: the Business Partnes Role Eternal erdos, you wl see Hat the option Is ‘there tohold data at Compan Code level and Purchasing Dat urder the single roe ONE- TIME VENDOR ‘Aone-time vendoris wed in cases where the vendor is oly used once or very rarely. This may be due to ‘an emergency, of geographical cicumstances for example where by /our typical supper canrot getthe ‘materialto youn the required time. Tygcaly, busivesies have rules in place tlt the use of onetime vendors, etier based on the number oftraxsactionso” a cap onthe amount spentwith them. The spend ith one-time vendors may bo managed through tho ice af a Purchasing Crdit Card (or Pata), oF thay ‘an be enteredin to SAP $/4 h asummarized manner through a onetime vendor acccunt. ‘The one-time vendor business partner creates 2 shall forthe split, whenyou use this recordin purchasng you arerequired wo nut address, and purchasing informatin (uch as payment ters) waro,poserrc RE rectly into the purchase order. The Busines Partner Grouping, which contro the number range used by tha record ie mapped tothe Vendor Account Group CED i the callocivoaccoust group usd for ono. me records lHyou wah to cieate a one time vendor record, you selecta number range sssecated witha Business Partnor Grouping that mape tthe CPD Vendor Account Grou: Having created the Purchasing Orgarsationview forthe Supplier, an entry will be made intable LFA ‘wien identfis thi record.asa cne-time account, using account group CPC: wano,poserrc RM GSS EVRD Se Ie eo aoe) (oe ‘When this rcord i subcequonty used ina purchase ardor, you re raquired topopulct the name and adress detalls ofthe supplier the ore-tme vendor record represents fer tis tansacton: VENDOR SUB RANGE ‘The Vendor Sub Range (VSR) canbe used tosubdhide the vrdor’s products into different ranges. For ‘example, homeimproverrent supplier may nave sub-ranges cf tool, construction products and servces. ‘This funationalty issu avallable mith the Suppl record in S/4 WANA on premise editon 1511 waro,oserrc ‘The VSR canbe entered into the purchasing information record oa particu suppler/materal ‘combinition, Tho allocation ofa matorialtathe VSR alews tho emeonthe purchace ardor to be cortad Insub range order ‘Confguration srequredto all Rs to be used. Ths configuration i stil held against the Vendor Account ‘Group in /4 HANAon premise eaten 1511, rather than the Busnes Partner Fol. The navigation path ‘or this configuation i IM > Lgltcs~ General > Business Partner > Vender > Control Define Account ‘Groups and Field Selection ‘One-Time Account a Genera Veneer bane roa carom cote Ox Speirs cane Oa Pacha ubo08 chang Pit ae | PutmerDetemBrocad, Panne scheme, puch on. (So) wb.nnge TI TABLES ‘The famliar Vendor tables from SAP Business Sule, LFA1 Supplier Nastar~ General Section) LEM (Wendor Master Record Purchasing Organisation Data), LEB (Vendor Master Company Code) and LFBK (Wendor Master Bank Details) are stil present inS/4 HANA on premise edition 1511 and are updating ‘ence the Busines Partner is e¢endad toa Supplier role and the appropiate data added waro,poserrc RE MIGRATION Only SAP ervienmments wth Customner/Vendor Integration in place can move teSAP S/4 HANA on premiceedtion 1511, SAP Business Suite sare can meve rom diferent start releases ‘to APS/AHANA, Towncue asucres:ulcomersion, al custanors abd suppliers must bo convortad ts BP (Businace Partners) inthesystem. Ths s ako tuefor the business partners that ate already in use. When the ‘ustomer/supplir transformation is triggered, the system posts all required fds in to business partner. ‘Suppliers are used widely in SAP ERP, byPurchasing and Accounting, and customizing settings have to be Imairtaired correctly so that éata can be converteé without additional settings. ‘The conversion from SAP Business Suite to S/4 HANA on premise edtion 1511 requires many technical ‘steps. This document covers only cenfiguration settings related tothe Vendor Master to support the ‘conversion. Before migrating toS/ HANA on premise edition 1511 it is dvisableto archiveand Vendor Mastar acerdethat aa fagge for deletion in SAP Business Suita, f these records are not archived they wil be ‘vancferred to /4 HANA cn prerrise edition 1511 with the deletion fag Prieto conversion the Sst vill carry out pre-checs ta ersure the conversion 6 valid. This requites several configuration steps. Fist you mus ersure thatthe Synchronsation is active for Business Partners. Ths isdone through manu path IMG > Cross Application Comgonents> Master Data Synchronsation > Synchronksation Control > ‘Smnchronsston Contrl > Activate PPO Requests for Patfrm Objects the Dialogue. Change View “Activation of the PPOs in the Dialog for Platform Objects % newenees (DO BR Action ofthe PPOs inne Deg f. Some Ponce ig Fe ‘The next checkis to ensure thatthe synchronisation i swirched on fro Business Partner to Customer, Business Partner to Vendor; along with Customer to Business Partner and Vendor to Business Partner ‘hiss danethrough menu path IMG> Cross Application Components > Master Data Synchronisation > ‘Snehronseton Contrel > Synchrenisaton Control > Activate Smnchronisation Options. vn ose Changs Vem active Sychroatention Options Overview gay °% New erows (FO (BB CE You must activate the creation of Post Processing Orders for component AP-MD through menu pathIMG > Cress Application Compenents > General Application Functions > Postprocessig Ofc > Business Processes > Actvate Creation of Postprocesing Orders. The Business Process CVI_O2 relates to the ‘Supplierto Business Partner Direction. Ater successful sypchronkation you anactawte CV 04 (direction Business Partner to Suppl) |fthanes Mew cacthents, Crantion of Boctnrocnnatad teres, Omari © H Newencis (DFO HE MB “The number ranges available for Vendors shoul be reewes through manu pth IMG> Lagtes General > Busnes Parter> Vendors > Control > Define Number Ranges fr Vendor Maser Records. sense I “This can then be cemnpared with the number ranges available forthe Business Partrer through manu path AG > Cross Application Components > SAP Business Partner > Basic Settings > Number Ranges and Groupings. woe nse 3 8 es E 8 8 js ol (ca o¢0os00000 wo seeocaoea at s100¢00000 {yo ceaosa0e0o sese9 ‘We insertes the nuber ranges forthe Suppler {and the Customer) n tothe existing Business Partner rumberranges. Were possible we kept the sare, this proved prebleratic withnurber range i for ‘example which was allocated to all cbjets, with dfferentto and from values. In ths easel for ‘convarson) wat eraated inthe Bucinase Parner numbar rang. ‘Toallow the Supplier and Business Fartnerto have the same dentife, the Busnes Partner number rangesare flagged as “enteral”. The numbering ill come from the Supplier. ‘nse encountered here was an estemal number range assigned tothe Custamer fo alshanumere entifcation had an upper limit of 82 (27277272). The Business Partner and Vendorhad an existing rnumberrange for something simlar, only the uoper limit here was 102 2722722272). in this case we ‘coule not insert a rurrber ange forthe Susiness Partner withthe Customers upper lini, due tothe fact iRoverlped. Thispoint highlights the needfor consistent configuration. wano oscar [EI IR Object waro,poserrc RE ‘To nombor ceo0002e00 o 0000100900 00399499 ao 10000800 100299198 a onooseon00 cxoos9s499 a ‘00000800 9399999898 a suooe0an00 sro00ost99 a ‘o10oseor00 0100889898 a x3 oxoseo0xe0 cxoasasts9 ma. rs 0700400000 ccoosess59 a ‘At tho Businose Partner lwo, the number rngesareaisiged toa Group rather than an Aecount Group, Cr Roe. Ths is done through menu path IMG > Cross Applcation Cormponents >SAP Business Partner > ‘usiness Partner > Bast Settings > Number Ranges & Groupings > define Number Ranges/Define Groupings and Assign Number Ranges. wano,poserrc [EI new cvs (0 EO ‘woigng shot ozve Int spore Betessoret [he can Wan reo Aso estnee “runPuter ramnPaee VO: Canr tan 22% Cam No Ran tre harber Asmat ‘Seema hunbe Asoent ‘Geers ninbe Asgrent ‘Seema nunte Asgoment ‘beers Minde Asgrent aan pert rt) ben harbe Asmat nestesat Poe () Tamayo (otra ‘Tau outne: (era) ee hurt Ase ‘eamununoe Asgoment ‘eam norte Augen ‘Beem Nurte Asgent Sgese9sss9s00s00s09sa90 ‘The Vendor Master Account Group i assignad toa Business Partrer Number Range Grouping inthe ‘mens path IMG@> Cross Application Components > Master Data Synchronisation > Custcmner/Suppler Integration > Business Partner Setings > Settings for Vendor Integration > Field Assignment for Vendor Incegaton > Assign Keys > Define Number Assignment for Direction Vendor to BP. SAP recoinenss that the Bushes Partner be asigned thesame identifier asthe suppler. There are certain lmtations to schicivirg this. Ac we have sean the Vendor an Customer may have everapsing number ranges, makingit Iinpoccible to croato the two raquirod Rusinace Partner numbor range and grouping. We aca face an lssuewhen a Vendor and aCustome exst withthe same dertiier, only one can keep thesame iertier forthe sssoclatad Busnes Partner waro,oserrc “There area nurter of BADI that may be activated forthe Business Partners (sich 25 form of addres) in this cae you should deactivate the enhancement CV_MAP_ITTLE_DIRECT andinstead activate ‘enhancement CVIMAP_BP_CATEGORY. ‘To support the Verdor to Business Partner Integration we need to define what BP roles) each Vendor ‘Account Groupperforins. You maintain tis through menu path IMG> Cross Application Components> “Master Data Synchronsation > Customer/Supplir Integration > Business Partner Settings > Settings for ‘Supplier integration > Define BP roe for direction Supper to BP. Note here how one Vendor Account ‘Group can map to multiple BF roles cepensing on the purpose ofthe Vendor Account Sfcup.A KRED ‘Vendor hol information at a Company Code and Purchasing Organisation Level for example, 50 maps to BP Roles Fl Vendorand Suppler, an Ordering Address (Account G-oup 0006) typicaly end hai Informationat the Purcating Organsaton ave, co woul map just aSupplir BP role nao ose no ro. Iti possible thatthe Industry Keys defined for Vendors and Business Partners do nat match, fn this case ‘the mapping must be established through menu path IMMG> Cross Application Components > Master Data ‘Synchronisation > Custorner/Supplier integration > Business Partner Settings > Settings for Customer ‘Integration > Field Assignment for Supplier Integration > Assign Attributes > Assign Industries. IF you are ‘converting irom an exstinginstance of SAP dusness Suteto SAPS/4 HENAN premise ection 111, the ‘conversion ore checkvallcates that these mappings exst "there are no entries inthese tables, te ‘conversion cannot proceed soe nse J waro,poserrc ‘The CV arecheck loge compares the number af entries in LAA (Vendors) with the numberof entries in ‘the mapping table CVI_VEND_LINK mapping tables. If Contact Persons are maintained atthe Vendor level, mapping table C”t_VEND_CI_LINKis checkes against table KNK and a comparison made against ‘the numberof records assigne dtoa Vendor eld LENR). Data Inconsistencies can revert the ‘generation of associated Business Partners, leading to a dcreparcy bewveen the two tables which prevents the conversion fem proceeding, Some examples of sheinconsatencies that may occur are: ‘+ Small addresses withoutan @ sgn 4+ Inconsistencies betweenthefielis settingsat Vendor Account Group level in SAP Business Sute and Business Partner Role inS/4 HANAOon premise edtion 1511, “+ Mising or incomplete customiaing settngs for tax numbers, categories, ingustries, '+ wrong ormat ror oats, rx codes, pank deta, postal codes, ete ‘The same checks performed against table KNA1 forthe number of Customers, and the mapring table (CV_OUST LINK ‘SAP fecommends thatcuscomerupalars ae gon the same number when convartng to 2 Businass Partner. By assigning identical numbers forthe Supplier ard BP, this saves confusion a the apoication level, preventing two cifferent numbers appearing forthe business partner in the one transaction. This may be problemaic the same number is assigned toa Vendor Master Recoré and an unrelated ‘Customer Master Fecord, inthis case one f the records should be glen a new BP number. fis ‘auviable to dedde't i more benetical fe he Castemer numbers to malzh the Bushes Partnar or the Vendor number to match the Business Farter. Ths way you cangenerate the Business Partners or the prefered funston, ensuring the correct numbering i utllsed: then generate the Business Partners for ‘the next function —with dfleringnurnber ranges as required. Here wewil look athe steps required t synchronise the Supplier number and Business Fartneraurmber ‘when thay are creates wth an iierral number rarge that ovelans ‘acinese Partner Number Range Configuration [erowine ‘Short Nane Naber Ot ito. internal Number]: zesignment | Asignnant NumberRange from No, “ToNarber AR Stat era a ‘pocoacoos | osgenocone | 5000 NO ‘Vendor Number Range Configuration | AccountGroup | Name Number Range waro rose ¢ RM om Sapa | ‘NumberRarge | From No. ‘ToNumber | NRStatus itemal ] o ‘oorcn900 | onoaigee2 | 100100 ND Inthis case, seeing as both number ranges ae actne and have been used, only the "To Number” vale ‘an be changed. You have to perform the following steps 4. Change the To Murnber inthe Business Partner incerval to 0000039338, 2. Create new number range, O2and mark it for exernal esignment Business Partner Intenals NurberRange [NS Siena ] o 5000 7 | o vis 2. Changethe BP Groupings toNumnber Range 02 ‘usiess Partner Number Range Asignent Grouping ‘ShortName | Descipton | Numberfange | itera J ‘0001 it Bo Trtoral Nursbar | Ot No Jsinrent | Asienment During the trarsformation the new Business Partners are now created out ofthe supplier with the same rumbers -Aftor the ntalioad, the umborrangos should again bo updated

You might also like