webRFC: Calling SAP function module from HTTP link

[Scenario: In the simple example, we will be displaying the material and the material group of the material code passed as parameter in the HTTPS url. The output is a text output.

1) Create a function module if it is a new requirement else use the existing one. 

The function module must have below parameters for this to work:

2) Release the function module.

3) Then release the function module for internet in transaction SMW0 using option displayed in below screenshot, (Internet release->Function Modules).

4) Activate WebRFC and provided login credentials in SICF: Path Server>SAP>bc>webrfc


Provide the user and password. This enables login to SAP system.
    This step is not required if the node is already active and has the correct login credentials. This can be          
    achieved using SAML configuration as well.

 5) The function modules can be called as explained below:

      http(s)://<your system>:<your port>/sap/bc/webrfc?        
      _FUNCTION=Z_WEBRFC_SAT&_Matnr=000000000008200006&_Name=<your userid>
     For example
    https://10.XX.XX.X/sap/bc/webrfc?     
    _FUNCTION=Z_WEBRFC_SAT&_Matnr=000000000008200006&_Name=SSHARMA.

We can add additional parameters in the path using ‘&’ as separator after function module.

6) Output: The output on clicking the link will be as below if material passed as parameter exists.

7) We can use MIME for returning images or binary files.

webRFC: Calling SAP function module from HTTP link

[Scenario: In the simple example, we will be displaying the material and the material group of the material code passed as parameter in the HTTPS url. The output is a text output.

1) Create a function module if it is a new requirement else use the existing one. 

The function module must have below parameters for this to work:

2) Release the function module.

3) Then release the function module for internet in transaction SMW0 using option displayed in below screenshot, (Internet release->Function Modules).

4) Activate WebRFC and provided login credentials in SICF: Path Server>SAP>bc>webrfc


Provide the user and password. This enables login to SAP system.
    This step is not required if the node is already active and has the correct login credentials. This can be          
    achieved using SAML configuration as well.

 5) The function modules can be called as explained below:

      http(s)://<your system>:<your port>/sap/bc/webrfc?        
      _FUNCTION=Z_WEBRFC_SAT&_Matnr=000000000008200006&_Name=<your userid>
     For example
    https://10.XX.XX.X/sap/bc/webrfc?     
    _FUNCTION=Z_WEBRFC_SAT&_Matnr=000000000008200006&_Name=SSHARMA.

We can add additional parameters in the path using ‘&’ as separator after function module.

6) Output: The output on clicking the link will be as below if material passed as parameter exists.

7) We can use MIME for returning images or binary files.

ALE IDOC configuration- Inbound

Inbound IDoc processing overview:

•             Go to transaction SE37 to create the function module if required for updating the table or SAP object from IDOC segments.

•          Go to transaction WE57 for assigning the FM to logical system. Specify FM name, function type, basic type (IDOC), message type and direction then save it.
• 

•         Go to transaction WE51 and make an entry for the inbound function module.
  
•         Go to transaction BD51 to define input method for inbound function module and click on Display change button. Specify your function module and input type by clicking the new entries.

        

•             Go to transaction WE42 and create process code. Also assign FM to the inbound process codes.

     

•          Assign the process code to the inbound processing message types in inbound parameters of partner profiles(WE20).

           

•         Go to transaction BD64 and generate the partner profile again.

•          Use program RBDAPP01 to process inbound IDocs. This program calls the FM configured in process code step 4.

Enhancement Implementation

Source Code Enhancement is one of the enhancement technologies available under Enhancement Framework. Implementing this technology is also called as Source Code Plug-In. Technically the source code plug-in implementations are stored in a separate include program and not as part of the original source program.

There are two types of Source Code enhancements possible.

• Implicit enhancement option
• Explicit enhancement option

Here I am explaining implicit enhancement. The screenshots in the explanation are for below scenario:
Extend materials (both header material and component material) to the plant while creation or change of BOMs.

Below are steps to create enhancement:

Step1:  Open include or function module to which you want to implement enhancement.

Step2:  In order to implement any of these Source code enhancements, you need to be in ‘change Enhancement mode’ (the spiral icon available in the editor) 

Step3: Goto Show Implicit Enhancement Options.   

Step4: Below lines consisting of double quotes(‘’) as shown in screenshot signifies that implementation is possible.

All Implicit Enhancement option will be displayed. In ABAP programs, implicit enhancement options are predefined at the following places:

·         Begin/End of an include.

·         Begin/End of Method/Function Module/Form Routine

·         End of a structure

·         End of Private/Protected/Public Section of a local class  

Step5: Right Click on the line and Create Enhancement as shown below. The options to modify the enhancement is also available in the list.

 

  
 

Give a name and create.
An option to decide type of enhancement will appear.

In the example it is ’Code’.

Step6: The editor will open in editable mode. Plugin the code as required and activate it.

Step7: Test and see how it works.

ALE IDOC configuration- Outbound + Change pointer

ALE IDOC configuration- Outbound
1. Use transaction “SALE/ BD54” to define logical systems.

2. Create RFC destination using transaction SM59

The server details like Host name, system number can be found in SM51.
Do a connection test to assure that is works.
ADS RFC connections cannot be tested using this. Execute program FP_TEST_00 to perform connection test.

3. Define port using transaction WE21 and provide the RFC destination created for the same.

4. Maintain Partner profile in transaction WE20:
Use the created port and configure all inbound and outbound messages.

5. Check if the change pointer is enabled or not using transaction BD61. Only if change pointer is applicable.

6. Activate change pointers for message types using transaction BD50. Only if change pointer is applicable.

7. Use transaction BD52 to configure change pointer by fields. Only if change pointer to is applicable.

8. Maintain distribution model using transaction BD64.

9. Custom filters can be created using t-code BD59 and can be applied in distribution model for applying special filter for IDoc distributon.

10. Create Serialization group using BD44. Table TBD40 if need to create idoc by object type serialization.

11. Add custom FM to generate IDoc using Change pointer in t-code BD60. Table TBDME

12. REBSER01 can used to generate IDocs using change pointers if Serialization Group is to be used. It generates IDocs in sequence defined in serialization group. Only if change pointer is applicable.

13. RBDMIDOC can be used to generate IDocs using change pointers.
[Program RBDMIDOX is used internally in both the above programs(step 12 and 13) to generate IDocs using change pointers for individual message types.]

14. RSEOUT00 can be used to set IDoc status from 30 to 03.

ABAP - Proxy Config from outbound System

TRANSACTIONS: SLDAPICUST, SPROXY, and SM59
Create proxy using transaction code SPROXY









Monitor sent messages using t-code SXMB_MONI
Destination system For ESR connection: Connection type: T

Destination system for Proxy. Connection Type: G

RFC for SLD connectivity. Connection type: T

RFC for connecting to PI ABAP system. Connection type: H.

RFC for connecting to PI integration server. Connection type: H.

Maintain SLD data in transaction SLDAPICUST also Maintain User ID and password.