Technology Blogs by Members
Explore a vibrant mix of technical expertise, industry insights, and tech buzz in member blogs covering SAP products, technology, and events. Get in the mix!
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

SAP HCI / Amazon AWS EC2 integration via SFTP (Ex. Electronic Invoice CFDI / NFe / GTS / others)

azael_navarro
Active Participant
‎09-20-2016 9:08 AM


Dear experts,

 

It is a pleasure to share a new Biz and Process vision adapted with the integration paradigm into this digital era with the new SAP Cloud / On-premise Strategy offer:

 

A. Business Vision:

 

It is time to understand that strategy doesn't deal only with an unknowable, distant future ("...2 or 3 years horizons is often more fitting..."). @BY Hambrick, D. J. Fredrickson so we can identify almost 3 questions here is: How digitalization has impact to my company?, What is my portafolio of KPI responses?... Are we prepared to design the best solution for challenges, for example about the transition to S/4 HANA (You can learn more about it-->Link

 

B. Process Vision:

 

I have dedicated this iFlow to electronic invoice process (i will not talk in deep) and more specific the standard implemented in Mexico called CFDI, to test this flow that allow to deliver an invoice between 2 cloud proposals after that the solutions could be implemented on-premise...

 

These kind of processes contain complex elements to consider like: legal aspects, standard contents, adapted logics, methodologies, investments, the talent considered for each solution, etc... But in particular commentaries, i can share the next little point of views:

 

  • For CFDI: do you remember the first legal considerations in Mexico?, when we had to implement both logics CFD & CFDI and even 4 versions at same time (2.0, 2.2, 3.0, 3.2) and each year more or less we have to update our solutions with new releases from SAP, for legal considerations and for custom requirements that sometimes are not best practices but simply are needed (without to explain more about this point)... Considerations as the landscape that you need to evaluate for example identifying if you will implement all notes for ECC or your SAP Simple Finance, Middlewares or BPM like SAP Process Integration / Process Orchestration (tech components: Java/XSLT/Graphical/UDFs Mappings, ccBPM/ICOs AE/IE Flows, etc...). And we can consider even the logic for our processes considering to centralize or descentralize our solutions with the help of partners called "PACs" like EDICOM... But the doubt here is: Do you still thinking that best practices for your current systems still being the "panacea", or Are you aware about "digital trends" that makes companies more scalable, simple and customer engaged?

  • For NFe: legal considerations in Brazil, the decision to consider standard solutions with SAP GRC where the costs are sometimes higher than to make a decision to implement custom solutions, where maybe you were working with R3 or more common with ECC and at same time to implement solutions with tecnologies like "Triangulus invoice system" to integrate business rules logics between or directly with your middleware and the SEFAZ...

  • For GTI: the third invoice process experience applied for china, that i had the opportunity to visualized is not far of other invoice solutions around the world, so you can consider files, soap, idocs and other logics used with java mappings if we still talking about SAP PI for example...


 

Common considerations: in this case you can consider interoperability with cloud or on-premise solutions delivered with partners like amazon, the linux repository to archive files like xmls, pdfs... or other providers specialized in electronic invoice where the general requirement is that your ERP or for example SAP Ariba deliver the information to initiate or complete the invoice process flow...

 

 

C. Technical Vision:

 

The focus is to show just the logic of an easy (after you achieve to implement it) but complex integration because you will find a lot of concepts in just few steps and as blog post dedicated to the CFDI with not real flow and information as maybe you can expect:

 

 

  1. Implement your Amazon Linux AMI instance:

    • In order to activate the SFTP service and to allow to archive the XML sent from HCI, you can follow the videotutorial where the process to follow is very similar: Getting Started with Amazon EC2 - Install, Configure, Connect - YouTube

    • You need to create your free account, you can activate easily your instance,

    • You must to consider components like: user (ec2-user), Public DNS / IP and to save your Key Pair for your firs entrance because after other configurations this will change to another Key...




  2. Implement SSH commands:

    • You need to follow the next pdf: http://sapassets.edgesuite.net/sapcom/docs/2016/05/a856cc5a-717c-0010-82c7-eda71af511fa.pdf

    • Main commands are:

      1. ssh-keygen -C "SFTP_SAP_HCI" -f SFTP_private_key

      2. openssl req -new -x509 -days 3650 -key SFTP_private_key -out SFTP_X509_certificate.pem

      3. openssl pkcs12 -export -in SFTP_X509_certificate.pem -inkey SFTP_private_key -out SFTP_X509_certificate.p12

      4. ssh-keyscan ec2-54-70-106-16.us-west-2.compute.amazonaws.com > known_host

      5. puttygen SFTP_private_key -O private -o SFTP_private_key.ppk (this was not implemented because an error appeared, so i just created the .ppk file using puttygen program and this file will be used at the end of the process to visualized your XML because the last .ppk will be unavailable to still using, even you will lose connectivity so you just need to change the .ppk file for recent),

      6. Dont forget to delete currect info and update with new row into "authorized_keys" file...



    • Main programs will be: WinSCP-5.9.2-Setup, puttygen, putty...



       



  3. Implement HCI iFlow:

    • You need to follow the next pdf: http://sapassets.edgesuite.net/sapcom/docs/2016/05/a856cc5a-717c-0010-82c7-eda71af511fa.pdf

    • You will need WinSCP to modify known_host file in order to get an Auth fail first error (is correct until this point) and kse-521-setup to integrate your id_rsa (the manual indicate 1 file but i imported 2 files because it seems that there is a little but important mistake: .pem for Tools/import trusted certificate and .p12 file for Tools/import key pair)...

    • In your tenant you have a password for your keystore system.jks, so in each password request to indicate or for new, please set the same...


    • Implement your iFlow and copy the XML CFDI dummy: El MashTer: Ejemplo xml de un cfdi 3.2




  4. Run your application:

    • When you deploy your iFlow in your tenant, the flow will be executed automaticaly because in this case we used Start Event in Run once,

    • After execution we can see a success flow:


    • And we can confirm that our CFDI XML File is now in Amazon:





 

D. References:

 

 

2 Comments
Labels in this area
Popular Blog Posts