Blog Archive

Thursday, July 30, 2015

Trading partner management in SAP PI and IBM sterling integration.

Om


SAP PI, B2B Add on 1.0 TPM description



IBM Sterling Integrator (redbooks)




In a simple ANY to ANY scenario over WebSphere MQ, the only field of importance is the
Network ID field. This determines which WebSphere Data Interchange Network profile is to
be used with this trading partner. This should correspond to the network ID selected in the
Mailbox profile as illustrated earlier. If Information Exchange is being used, the user is
required to enter an Information Exchange Account and User ID. It will also be necessary to
identify the Interchange Attributes by entering the Trading Partner's Qualifier and ID. The ID
in this instance could be an alias, depending on what you have defined in Information
Exchange.
In WebSphere Data Interchange's view of the world, there are two type of trading partners:
application (or internal) trading partners and EDI (or external) trading partners. An application
trading partner represents a business entity within the customer's enterprise. An external
trading partner is a business entity that the user's enterprise does business with via EDI. Both
are represented by a Trading Partner profile. What differentiates the two of them is the trading
partner type field on the General tab of the Trading Partner Profile editor. In Figure 1-23, we
see that ANY is defined as being both an EDI and application trading partner.
WebSphere Data Interchange provides tabs to store more specific details on the trading
partner. For example, space is provided for company information and contacts. These are not
required.

Tuesday, July 21, 2015

IBM Maximo/Tririga and SAP PI integration using SOAP,IDOC,HTTP adapters

Om


I did not find relevant information from scn sap the way to integrate TRIRIGA with SAP PI, Later searching information on tririga and maximo( both are IBM product related), and observing integration documents of IBM. I have found some information.

search the IBM knowledge center for the guides of MAXIMO and SAP PI integration. 


For swcv, you need to import tpz files in your SAP PI and created business component and communication channel as said in the manual document of ibm maximi/tririga.



From tririga manual.


Integrating data with external applications

You can use the IBM® TRIRIGA® Application Platform connector tools to insert, update, or export data from your IBM TRIRIGA database.
Setting up an SAP Crystal Reports server for IBM TRIRIGA and setting up Crystal Reports for use in IBM TRIRIGA applications
You can run reports that are created in Crystal Reports in your IBM TRIRIGAapplications. You must configure a Crystal Reports server. You must also configureIBM TRIRIGA applications so that you can display the output from Crystal Reports in 

Thursday, July 16, 2015

important Business transactions flow to understand

Om



MM Flow in SAP( buyer /customer/client)

 =>MRP Controller(md11)
=> purchase requisition(me51N) 
=>request for qotation(me41) 
=> purchase oredr(me21n) 
=>order confirmation (va01) 
=> gooda receipt (migo) 
=> material documentation(mb51) 
=> invoice verification(miro)
=> physical inventory document (inventory counting, cycle counting, clear difference)


SD FLow in SAP(seller/vendor)

inquiry(va11) 
=> quotation(va21) 
=> purchase order(me21n) 
=>saleorder(va01) 
=>delivery(VL01N)
=>SHIPPING(VT01) 
=> BILLING (VF01)
=>INVOICE(VF21)

B2B addon mapping content made easy with content manager EDI to XML conversion and vice versa also with XSD generation

Om

EDI mappings are made easy for SAP idoc Integration.

Most of the time, client has sample EDI files, for which you need to integration with SAP System (by using IDOC message types)

Content manager Provide: provide required xsd for EDI messages (based on version)



Simplify message mapping content by using EDI to XML conversion option in content manager


As shown above, you can map delimiter as *, and different options along with the spaces;
By Observing the above xml content , you can guess the required target mapping logic

Using conversion module in file adapter to convert ( EDI ßà XML vice versa)


and different module parameters as below

EDI-XML Converter Module Name
Parameter Name
Description
EDIFACT
edifact.encoding
This parameter specifies the encoding of the EDI message (not of the XML). The default value is ISO-8859-1.
edifact.copy
This parameter adds the source message as an attachment to the PI message before the actual conversion starts. The default value is false.
edifact.namespace
This parameter specifies the namespace of the XML document.
edifact.indent
This parameter formats the messages with CRLFs and tabs. The default value is false.
edifact.audit
This parameter logs all the processes carried out by the converter module.
edifact.trace
This parameters tracks all the processes involving the converter module.
edifact.monitor.ackstatus
This parameter enables the acknowledgement logging in the converter module.
EANCOM
eancom.encoding
This parameter specifies the encoding of the EDI message (not of the XML). The default value is ISO-8859-1.
eancom.subversion.prefix
This parameter allows you to define the subversion name either as EAN or GS.
eancom.indent
This parameter formats the messages with CRLFs and tabs. The default value is false.
eancom.copy
This parameter adds the source message as an attachment to the PI message before the actual conversion starts. The default value is false.
eancom.namespace
This parameter specifies the namespace of the XML document.
eancom.audit
This parameter logs all the processes carried out by the converter module.
eancom.trace
This parameters tracks all the processes involving the converter module.
ODETTE
odette.encoding
This parameter specifies the encoding of the EDI message (not of the XML). The default value is ISO-8859-1.
odette.copy
This parameter adds the source message as an attachment to the PI message before the actual conversion starts. The default value is false.
odette.indent
This parameter formats the messages with CRLFs and tabs. The default value is false.
ANSI ASC X12
x12.encoding
This parameter specifies the encoding of the EDI message (not of the XML). The default value is ISO-8859-1.
x12.copy
This parameter adds the source message as an attachment to the PI message before the actual conversion starts. The default value is false.
x12.indent
This parameter formats the messages with CRLFs and tabs. The default value is false.
x12.checkOfValueMinLength
This parameter ensures that the converter checks whether all data fields fulfill the minimal length restriction. The default value is false.
x12.fillUpToMinlength
This parameter ensures that the converter automatically fills up the data fields until the minimal length restriction has been reached. An error is displayed if the minimal length restriction is violated. This parameter is useful only if x12.fillUpToMinlength is activated.
x12.monitor.ackstatus
This parameter enables the acknowledgement logging in the converter module.
TRADACOMS
tradacoms.encoding
This parameter specifies the encoding of the EDI message (not of the XML). The default value is ISO-8859-1.
tradacoms.copy
This parameter adds the source message as an attachment to the PI message before the actual conversion starts. The default value is false.
tradacoms.indent
This parameter formats the messages with CRLFs and tabs. The default value is false.
VDA
vda.encoding
This parameter specifies the encoding of the EDI message (not of the XML). Default value is ISO-8859-1.
vda.copy
This parameter adds the source message as an attachment to the PI message before the actual conversion starts. The default value is false.
vda.indent
This parameter formats the messages with CRLFs and tabs. The default value is false.
PLAIN
plain.copy
This parameter adds the source message as an attachment to the PI message before the actual conversion starts. The default value is false.
plain.indent
This parameter formats the messages with CRLFs and tabs. The default value is false.
Generic
edi.copy
This parameter adds the source message as an attachment to the PI message before the actual conversion starts. The source message can be a supported EDI format. The default value is false.
If you are using SAP NW 7.31 providelocalejbs/AF_Modules/MessageLoggerBean as the module name, and then define the parameter name aslog.condition and log.location to ensure persistence for outbound scenarios.

supported encoding:
http://docs.oracle.com/javase/6/docs/technotes/guides/intl/encoding.doc.html


Validating and GOOD GUI for EDI messages using (Liaison tool) free to install like notepad ++