Equipment Record Integration With External System via IDOC

8/18/2019 Equipment Record Integration With External System via IDOC

1/11

Equipment recordIntegration with external

system via IDOCcreated by Karthi Selvanayagam on 29-Aug-2014 04:42, last modifed by KarthiSelvanayagam on 29-Aug-2014 0:2!"ersion 1inShare

1. SA Equipment !ecord "unctionality

#he e$ui%ment record is uni$ue in&ormation associated 'ith a material number, and a corres%ondingserial number &or the material in SA() #his document basically can be categori*ed into t'o ma+or segments

o #he &unctionality &eatures available in e$ui%ment record in SA()

o And &ocuses on the integration o& e$ui%ment masters 'ith other eternal a%%lications 'ith hel%o& .docs

/a+orly in . #ech industries the business tracs these e$ui%ments in several 'ays,its inventoried 'ithin the %lant 'ith e$ui%ment numbers, and stoc trans&ers aredone to 3istribution centers 'ith Serial numbers) And lot o& customer 5ndconsumer in&ormation is stored in the 5$ui%ment record &or &uture su%%ort %ur%oses

#. $usiness purposes o" Equipment

o 5$ui%ment records are delivered to customer sites)

o 5$ui%ment numbers 6serial numbers7 consumed in a %roduction order as com%onents

o Shi%%ed &rom stoc, Shi%%ed to certain %artner locations &rom 'here it undergoes installation%rotocols

o Set o& 5$ui%ment records are then batched &or customer acce%tance "ia SA( 8/

o 3ata u%dates ha%%en on the 5$ui%ment records at various stages o& the business, Addressdetails are u%dated in the e$ui%ments)

o 8ustomer acce%tance is done 'ith e$ui%ment record numbers)

o /aterial returns are taen bac at %lants 'ith serial numbers 5$ui%ment record)

%. &igh level Integration 'ow

http://scn.sap.com/people/karthi.selvanayagamhttp://scn.sap.com/people/karthi.selvanayagamhttp://scn.sap.com/people/karthi.selvanayagamhttp://scn.sap.com/people/karthi.selvanayagamhttp://scn.sap.com/people/karthi.selvanayagamhttp://scn.sap.com/people/karthi.selvanayagam


2/11

(. artner "unctions de)nition and assignment

#he &eature in e$ui%ment record, allo's you to defne assign %artner &unctions in them)

o Sold to (arty

o Shi% to %arty

o .nstallation %artner

o ill to (arty

#he 5$ui%ment used in a customer delivery can automatically co%y the values &rom the Sales order ora delivery and assign the %artner &unctions value in the e$ui%ment)

#he %artner &unctions could be driven later on &or illing relevant re%orts, it gives in&ormation on 'hiche$ui%ment is delivered or categori*ed 'ith that sold to or ill to customer)


3/11

*. Class + characteristics in Equipment record

#here is a %rovision 'here you could defne class 'ith characteristics 'hich can be assigned to an

e$ui%ment record8lass ty%e 002 ; 5$ui%ment class can be created and assigned to e$ui%ments

/ainly the undle in&ormation in e$ui%ment is stored in the %icture above, but other'ise any%arameter related to the e$ui%ment could be stored as details in the characteristics)

,. Custom status in Equipment record

#he Standard SA( status in an e$ui%ment indicates the 3elivered in stoc Available statuses)ased on customers re$uirement the


4/11

#his is the 5$ui%ment vie' ; 'here the user status %rofle is assigned, and it sho's the di=erent levelo& the statuses) #hese statuses can be manually changed 'ith .502 or .>02, but in the currentintegration the .nbound .doc to 588 controls the status set)

?)1 8onfguration menu &or the


5/11

-.Additional data a/ in Equipment record

#he other im%ortant &eature 'hich is im%lemented is the "ie' %rofle change in the 5$ui%ment) #hisgives the @eibility &or the users to add more details, basically the end customer relevant in&ormationlie customer hierarchy, ocation 'here the device is set, the . ( address o& the e$ui%ment, and muchother consumer in&ormation can be stored

-.1 De)ning the view pro)le


6/11

-.# Assign the view pro)le to the equipment level0 Equipmentcategory


7/11

art # o" this document a/out the Idoc A2E technicalsetups

3. Idoc Settings o" the Equipment record #code B5C1 Be 'ill need message ty%e &or 5$ui%ment integration through .3D8) Eor this 'e may use the eistingmessage ty%e available in the system or create a ne' message ty%e using #code B5C1) ere 'e usethe eisting message ty%e in the system)

#code B5!0 B5!1

Be have created custom .3D8 to handle our re$uirement) #his .3D8 'ill containthe standard sturctures and structures to hold the address o& the e$ui%ment and the

custom felds) #he address 'ill be %assed using the segment 51(A31" 'hich isco%ied &rom standrard A3/AS01 .3D8 and the custom felds are %assed usingcustom segment

#code B5C2


8/11

Be have assigned the eisting e$ui%ment create message ty%e to the .3D8 'hichcreated in the %revious ste%) #his is re$uired &or both the inbound and outbound.3D8 %rocessing as 'e need message ty%e &or each .3D8

9. Inbound IDOC settings: #code B5F

.nbound .3D8s are %rocessed by Eunction modules) Be co%ied the standard&unction grou% .#DGA(.G5> to a custom &unction grou% including the &unctionmodules to custom &uction modules to 'rite additional logic to u%date address andthe custom felds) #hen 'e have to confgure the custom &unction module co%ied&rom the standard &unction module .3D8G.H(


9/11

10. Outbound IDOC settings:

Settings for change pointer:

8hange %ointers are created 'ith res%ect to message ty%es) Eor each message ty%e i& the setting is

there it 'ill create a change %ointer).n #code 30, message ty%e should be enabled &or change %ointer creation)

.n #code 32, the felds 'ere mentioned &or 'hich the change %ointer should be added) Eor ourscenario, 'e need to send .3D8 &or any change in the e$ui%ment, 'e set the table ey as the change%ointer feld and 'e override the change %ointer creation using the A3. mentioned belo')

.n #code 3?0, a &unction module should be assigned) #his &unction module 'ill tae care o& creating

.3D8s &rom the change %ointer) Dur &unction module is a co%y o& the standard &unction module/AS#5.3D8G85A#5GS/3G5>


10/11

11 Integration:

Create change pointer4

Bhenever e$ui%ment is changed, 'e have to send the changes to other %arty via.3D8) ecause o& having large number o& additional felds and the felds may beadded more in the &uture, also user status is not in the 5>


11/11

Equipment Record Integration With External System via IDOC

Documents