terça-feira, 30 de agosto de 2022

Configuring HTTP Content Server (2) – Save printed document (1/2)

 I will not speak about installing and configuring the HTTP Content Server, there is already very good documentation about it. Here we will see how to use the content server to store printed document.

For the example, I will used the Sales Order in an IDES Server.

Configuring the output

The configuration of the output is done using the transaction NACE.

/wp-content/uploads/2014/01/nace_1_362099.png

To configure Sales Order output, you have to select the Application “V1” and press the button “Output types”

/wp-content/uploads/2014/01/nace_1_362099.png

The standard Output Types for the sales order is BA00, I will use it.

Select the Output type in the right part, and double click on “Processing routines”.

/wp-content/uploads/2014/01/nace_1_362099.png

The configuration of the Output type “BA00” for printing is this one. Program “ZSD_RVADOR01” and Smartform “ZSD_SALES_ORDER”.

Now we could open a Sales Order and check if the message BA00 works.

Transaction VA02.

/wp-content/uploads/2014/01/va01_1_362126.png

Press the button “Print preview” to display the default output type :/wp-content/uploads/2014/01/va02_4_362135.png

/wp-content/uploads/2014/01/va02_5_362136.png

The Smartforms works (good).

To display witch output type was used, you have to go in the menu :

/wp-content/uploads/2014/01/va02_2_362127.png

/wp-content/uploads/2014/01/va02_3_362128.png

This output is yellow because it’s not already processed. Print preview doesn’t process the message, even if you print during a preview !

To configure the automatic creation of this message you have to configure the transaction VV12.

/wp-content/uploads/2014/01/vv12_362137.png

(in your system, you could have several key combinations, for example to be able to specify the printer by plant / sales org / …)

if you go in detail of the condition record you will see something like this :

/wp-content/uploads/2014/01/vv12_362137.png

In this doc, we will try to use the option of the last parameter :

/wp-content/uploads/2014/01/vv12_362137.png

Configure the archiving of the Sales order

A long preparation for a quick configuration ..

Define document type :

Transaction OAM1, go in the menu :

/wp-content/uploads/2014/01/oam1_362832.png

(or directly using transaction OAC2)

/wp-content/uploads/2014/01/oam1_362832.png

I specify to the system to save the document in PDF format. I could set “*” if I will be able to store PDF, Word, Excel, …

Define the links

Transaction OAM1, go in the menu :

/wp-content/uploads/2014/01/send_362319.png

(or directly using transaction OAC3)

The key corresponding to Sales Order is VBAK :

/wp-content/uploads/2014/01/oam1_362832.png

In the OAC3 trans. we specify for this kind of document to store the document in the ContentRepository Z1 and to use the link table TOA01.

(You could use 99 link tables TOA01 -> TOA99)

Save it

Test

Now, we come back to the configuration of the output type in the VA02 transaction.

(menu : Extras -> Output -> Header -> Edit)

/wp-content/uploads/2014/01/oac3_362327.png

Select the line and Click on the button “Communication method” and select “Print & Archiv”

/wp-content/uploads/2014/01/oac3_362327.png

(don’t forget to set with the button “Further Data” : “Send immediately” )

Back and Save.

Result

In transaction VA03, go in the output type.

/wp-content/uploads/2014/01/oam1_362832.png

Select the line and go in the menu :

/wp-content/uploads/2014/01/oam1_362832.png

With Sales order you will have a popup like that, but with others transaction like Invoice you won’t.

/wp-content/uploads/2014/01/oam1_362832.png

Double-click on the document will open you an internet browser :

/wp-content/uploads/2014/01/oam1_362832.png


Source: https://blogs.sap.com/2014/01/13/configuring-http-content-server-2-save-printed-document-12/

SD & EDI Transactions

 

Transactions

  • search_sap_menu - Finds the menu path to a transaction - Can either type in TX code in the search criteria or a description- ie. 1st try SE38 and then ABAP.... the returned result is 'bottom to top'.

  • VOE1        Translation between EDI categories and SD item categories

  • VOE2        Table EDSC view. Customer link to sales area detail

  • VOE3        Table view EDPVW. Add partner types that will be transferred to the IDoc

  • VOE4        Table view EDPAR. Link external partner number with our internal number

  • WEDI        EDI Administrator Menu

  • BALE        Idoc Administration

  • OVA9        Create entries for each sold-to customer for which you will receive EDI schedule releases.  At implementation, the only field that needs to be maintained is "Check PO number," which causes SAP to make sure that the PO number sent on the release matches the PO number on the schedule agreement. This transaction updates table T663A.  SAP will not post an EDI schedule release, if this record is missing.

  • OVAI         Create entries for each Vendor / Partner description combination.  (Vendors must match sold-to Acct. at Cust., and Partner descriptions must match ship-to Partner descriptions.) This transaction updates table T661W.  SAP uses this table to determine the schedule agreement sold-to partner.

  • OVAJ        If you would like SAP to post schedule requirements using discrete dates only, instead of weekly and/or monthly buckets, you can indicate the days of the week that you deliver to this customer.  SAP will divide the customer's quantity for a week or month evenly into the days of the week specified by the distribution function code.  This code must be sent in the DELINS IDoc in field E1EDP16-ETVTF.

  • WE09 / WE02    IDoc lists according to content. View IDocs via specific IDoc number or business application detail contained within the contents of a segment.

  • WE05        View IDocs

  • WE19        EDI test tool. Use to test inbound Function module changes.

  • WE20        Partner profile configuration. Add partner detail together with inbound and outbound relationships. We also incorporate message control on the outbound IDocs. Utilize the organizational units to trap functional errors for further processing

  • WE30        Create IDoc extension type

  • WE31        Segment create

  • WE57        Assign function module to logical message and IDoc type

  • WE60        IDoc type documentation tool

  • WE82        Link Release detail to Extension IDoc Type

  • BD55         Conversion rule user exit. Link conversion rule user exit to the different system \ partner combinations

  • BD87         Reprocess IDocs in error or waiting for action. (Both inbound and outbound in 4.6. Use BD88 in prior versions)

  • BALA        ALE Application Distribution

  • BALM        ALE Master Data Distribution

  • V/36          Maintain output determination for deliveries (Output determination procedures). V10000 (Header output) has condition type LAVA (usually with requirement 1 NB: Use V/84 – V7ALLE – SHAD for grouped ASNs. I.e. Group deliveries into shipments

  • VV21,VV22,VV23          Create output condition records for shipping. LAVA – WE (Partner function) - We must add each new partner with VV21

  • VL71         Reissue output for deliveries

  • V/54          Maintain access sequence for billing documents

  • VV31,VV32,VV33          Create condition records for billing documents. (RD00 – RE Billing party)

  • VF31         Reissue output for billing documents

  • V/30          Sales document output types (BA00)

  • V/48, V/32, V/43            Maintain access sequence for sales documents

  • VV11,VV12,VV13          Create condition records for sales documents. (BA00 – SP Sold to party)

  • V/27          Create code to check requirements for output control. Used to check ZBA0 against BA00 output.

  • VA02         Sales order change

  • VA05         List of sales orders

  • VA22         Quotation change

  • VA32         Scheduling agreement change

  • VA42         Contract change

  • VF02         Change billing document

  • VF11         Cancel Billing document

  • VF04         Billing due list

  • FBL5N       Display Customer invoices by line

  • FBL1N       Display Vendor invoices by line

  • VL02N       Change delivery document

  • VL04         Delivery due list

  • VKM5        List of deliveries

  • VL06G       List of outbound deliveries for goods issue

  • VL06P       List of outbound deliveries for picking

  • VL09         Cancel goods issue

  • VT02N       Change shipment

  • VT70         Output for shipments

  • VKM3, VKM4    List of sales documents

  • VKM1        List of blocked SD documents

  • VD52         Material Determination

  • SWEAD     Event queue administration

  • SWE2        Event type linkages

  • SWE3        Event linkages

  • PPOME     Organizational Unit Maintenance

  • SWE5        Consistency Checks for Event Linkages

  • SWUD       Workflow Diagnostic Tool

The following section provides detail on other useful SAP areas.

Once the order is saved proceed through the following steps. The process assumes the item has values in the warehouse bin.

  • VL04         Delivery due list. Run the delivery due with your order number to create the delivery

  • LT03         Create Transfer Order. EG. Warehouse: 101 and enter. Picking background. Save

The Transfer order should now be saved. It now needs to be confirmed.

  • In LT03 go to menu option Transfer Order -> Confirm – Transfer Order
  • Enter
  • Save

The transfer order is now confirmed.

  • VL02N       Delivery change. EG: Edit the delivery to do the following Pack – External customer material number = COO. External delivery number – Waybill number. BOL – Transport tag. Carrier – Header partner – SP (E.G. FXP). Tracking number = Packing Unit

  • ME22N      PO Change

  • ME57        Create PO from purchase requisition

  • MIGO        Post goods receipt

  • MD04        Material Requirements. Shows material requirements and releases against materials

  • SE38         ABAP Editor. Used to modify ABAP programs

  • SM01        Transaction list. Lock transactions in the system. Also a good tool to see what transactions are available

  • SHDB        Transaction recorder (BDC)

  • CMOD       User exit \ project tool. Coordinates your changes into projects for the purpose of activating all user exits for a particular project. A user exit needs to be modified before it will work

  • SE16         Table contents display

  • SOST        View mails sent externally from SAP

  • SU53         Check authorization object

  • SQVI         Table Quickviewer – Used to created quick client dependent reports

  • ST22         ABAP Dump Analysis

  • ST01         System trace

  • ST11         Display developer trace

  • ST05         SQL Trace

  • SM21         System log

  • ST22          Display short dumps

  • SM12         Display locked entries 

Programs

  • RBDAPP01       Post inbound Idocs to application documents

  • RBDAGAI2        Re-processing of IDocs after ALE input error

  • RBDAGAIE       Reprocessing of edited IDocs

  • RBDMANIN       Start error handling for non-posted Idocs

  • RSEINB00         Idoc inbound processing by file

  • RSEOUT00       Process outbound IDocs

  • RV80HGEN       Report 'RV80HGEN' for including customer-specific routines in the SAP standard source code is not included automatically as an XPRA in the object list of the transport request. See OSS note 0385067. This report needs to be run in target clients once you have implemented a custom requirements definition.

  • RSWUWFML    Report that interrogates the Workflow inbox, based on certain selections, and then forwards a notification to the respective users that they have email waiting in the SAP system. The auto-forwarding assignment of an email address to a user can be accomplished by the administrator and tx: SO36 or by the user themselves using tx: SO13. Use tx: SOST to view email status’ sent from SAP.

  • RHSOBJCH      Corrects the following error in workflow customizing:

Transport object PDST

Information Table SOBJ is consistent as regards key tables

***Error*** Table HRP1600             Not an entry in table SOBJ

Information Table SOBJ is consistent as regards PAD tables

See note 134311 (point 2). Note 60801 also recommends the same steps regarding RHSOBJCH.

  • RSPO0075 Run report RSPO0075 to activate access method M for device types.

Source: http://www.swsc.net/db/sap/doc_page52.html

Integrating MM & SD Modules in Same Client to Create Sales order in Supplying Company Code Using PO raised in Receiving Company Code By I-Doc Message Type ORDERS Part1

 Hi Friends in this document I’m going to explain about integrating purchasing and sales process between different company codes maintained in same server & client by using EDI & I-Docs with message type ORDERS. Once the Sales order is created in Supplying company code, confirmation is sent to receiving company code by using message type ORDRSP.

Prerequisites:

  1. Knowledge of MM & SD
  2. Two organization structures: one for purchasing and another for sales

          Purchasing: Company Code:8888, Plant: 8881, Purchase Organization: 8881,

          Sales: Company Code:6666, Delivering Plant: 6661, Sales Area:6666, 66, 66, Shipping Point 6666.

  3. Basic I-Docs knowledge

Steps:

  1. Check Logical system assigned to your client in transaction SCC4.


/wp-content/uploads/2013/08/1_266334.jpg

2. Create RFC destination (of type  ABAP Connection)  to the logical system in transaction SM59. Here give the same name as of logical system & fill target host & system number as shown below. In logon & security Tab fill client, username & password. To check the connection click on Remote logon & connection test. If you are able to remotely log in to target client then  proceed to the next step.

/wp-content/uploads/2013/08/2_266338.jpg

3. Create a port of type Transactional RFC in transaction WE21. You can give port name manually or else system will assign one based on your selection. select I-Doc version as SAP release 4.X & give RFC destination name which was created in Step No.2 .

/wp-content/uploads/2013/08/3_266349.jpg

4. Create Vendor Master in Transaction XK01 with Organizational elements of Purchasing System i.e, Company Code:8888 & P.Org: 8881. In Correspondence Company Code data, maintain  Account with Vendor field  with the customer number that you will create in Step No.7

/wp-content/uploads/2013/08/15_266351.jpg

5. In transaction WE20 create Partner of type LI(Vendor) & give the vendor number created in Step No.4 & Save it. Now Click on ‘+’ button in outbound parameters area as shown below.

/wp-content/uploads/2013/08/4_266350.jpg

6. Enter the Partner Role VN and select message type as ORDERS.

In Outbound options tab, enter the receiver port which was created in Step No.3. Select the transfer idoc immediately to transfer the Idoc as soon as it was created. Select the Basic type as ORDERS05

/wp-content/uploads/2013/08/5_266353.jpg

In message control Tab Enter the Output Message type of Purchaser order Ex. NEU as shown below and select process code as ME10.

/wp-content/uploads/2013/08/6_266378.jpg

In EDI Standard Tab maintain as shown below. For more details press F1 in that particular field.

/wp-content/uploads/2013/08/7_266379.jpg

7. Create Customer Master in Transaction XD01 with organizational elements of Sales System i.e., Company Code:6666 Sales Area: 6666, 66, 66. In correspondence company code data, maintain Account at customer field with vendor number created in Step No.4.

/wp-content/uploads/2013/08/16_266352.jpg

8. In transaction WE20 create Partner of type KU (Customer) & give the Customer number created in Step No.7 & Save it. Now Click on ‘+’ button in outbound parameters area as shown below.

9,2.jpg

Enter the Partner Role SP and select message type as ORDRSP.

In Outbound options tab, enter the receiver port which was created in Step No.3. Select the transfer idoc immediately to transfer the Idoc as soon as it was created. Select the Basic type as ORDERS05

9,3.jpg

In message control Tab Enter the Confirmation Message type of Sales Order Ex. BA00 as shown below and select process code as SD10.

9,4.jpg

In EDI Standard Tab maintain as shown below’ For more details press F1 in that particular field.

/wp-content/uploads/2013/08/7_266379.jpg

9. In transaction WE20, expand Partner type LS(Logical System) & select the Logical system which was assigned to your client in Step No.1 (This Logical system already exists & don’t required to create).

/wp-content/uploads/2013/08/8_266399.jpg

Now Click on ‘+’ button in inbound parameters area as shown above. Select message type as ORDERS.

In Inbound options tab, Select the process code ORDE and select trigger immediately & to process the I-doc immediately.

9,1.jpg


10. Similarly maintain inbound parameters for message type ORDRSP to the same logical system with process code ORDR (order confirmation)

11. Create Condition record in transaction NACR for message type NEU (purchase order Print out EDI) with combination P.Org & EDI Vendor.

/wp-content/uploads/2013/08/10_266408.jpg

Enter the P.Org:8881 & Vendor:2096 and press enter. Select Medium 6(EDI), 4(send immediately) & Language EN)English). Then save it.

11,1.jpg

Note: The partner role selected here is used as partner role in Step No.6.

Note: In message control tab you have to maintain this message(NEU) in step No.6.

12. Similarly Create Condition record in transaction NACR for message type BA00(Sales Order Confirmation) with Combination Order Type.

11,2.jpg

Enter the the sales order document type ‘OR’ and press enter. Select Medium 6(EDI), 4(send immediately) & Language EN)English). Then save it.

11,3.jpg

Note: The partner role selected here is used as partner role in Step No.8.

Note: In message control tab you have to maintain this message(NEU) in step No.8.

13. Create Material master in Transaction MM01 with organzational elements of purchasing system i.e., Plant:8881. Maintain basic data, purchasing, plant storage data & accounting views. Fill Gross weight & net weight fields in basic data tab. remaining as normal.

/wp-content/uploads/2013/08/12_266424.jpg

14. Extend the material created in Step No.13 in transaction MM01 with organizational elements of Sales system i.e., Plant:6661, Sales Area:6666, 66, 66. Maintain Sales1&2, sales plant data, storage plant data, accounting views.

/wp-content/uploads/2013/08/13_266425.jpg

15. Create standard purchasing info record in Transaction ME11, with vendor:2096, Material; 2070, P.org:8881, Plant: 8881.

14,2.jpg

In General Data maintain Vendor Material Number field with material Number in Sales system (Same number as both systems are using same material number). In Condition tab maintain Gross price. Ex. Rs.300 per TO

14,3.jpg

16. Create Condition Record for inputTax Condition type MWVS in transaction FV11. Slect key combination Ex.Domestic Taxes. Where i4 is the Input tax code with 10% input tax in Country India

/wp-content/uploads/2013/08/20_266428.jpg

17. Create Condition record For Gross Price Condition Type ‘PR00’ in transaction VK11 with required key combination & maintain the Gross Price. Ex.300 Per Tonne

/wp-content/uploads/2013/08/17_266437.jpg

/wp-content/uploads/2013/08/18_266435.jpg

18. Create Condition Record For output tax condition type MWST in transaction VK11 with required key combination. Where S1 is the ouput tax code with 10% output tax in country India.

/wp-content/uploads/2013/08/19_266436.jpg

19. Maintain the Sales Area for the Customer & vendor combination in Transaction VOE2

/wp-content/uploads/2013/08/21_266438.jpg

Note: Maintain the vendor number manually(as there is no search help) with prefix zeros if required as SAP will look for the same.

20. Convert External Partner Numbers to internal partner numbers. Here we have to convert external ship to party(8881 receiving plant) to internal ship to party 100211. To achieve this make entries as below in Transaction VOE4.

/wp-content/uploads/2013/08/22_266439.jpg

21. In your sales pricing procedure make sure that condition types EDI1 & EDI2 exists at the end of the schema as shown below. Those two condition types stores unit price and total value of item expected by customer(i.e., Price maintained in PO). These two condition types are for information purpose & can be used for blocking sales order & billing if the price differs from price in sales order. Transaction V.25 is to be used to release from blocking.

PRICING EDI.jpg

Testing:

Step1. Make sure the stock exists in delivering plant(6661). Then Create PO in Transaction ME21N in receiving plant 8881

/wp-content/uploads/2013/08/23_266440.jpg

In PO Item Materials Data tab observe vendor material number field filled or not. if you haven’t created info record you can maintain manually.

In Confirmation tab maintain Confirmation Control key as 0001(Confirmations) & mark Acknowledgement required check box.

In messages observe NEU message was triggered with medium 6(EDI). Save the PO & make sure PO message was sent. Use transaction code ME9F if required.

Step2: In Transaction WE02 Check the outbound I-doc Status of message type ORDERS.

/wp-content/uploads/2013/08/24_266447.jpg

/wp-content/uploads/2013/08/25_266448.jpg

Here Idoc 911045 as shown above. If it is successfully processed it will have status 3.

Step3. Then Check Inbound IDoc of Message type ORDERS. Here the IDoc 911046. If it is successfully processed and have status 53 then get the sales order number as shown below. 

/wp-content/uploads/2013/08/26_266449.jpg

Step4. Open the sales order in Transaction VA03. Obsrve PO Number, order quantity, delivery date & customer material number.

/wp-content/uploads/2013/08/27_266453.jpg

In item Conditions Tab observe condition types EDI1 &EDI2 are updated with Unit price & total value of material ordered in PO respectively

/wp-content/uploads/2013/08/28_266454.jpg

In item Order data tab observe below details

/wp-content/uploads/2013/08/29_266455.jpg

Step5. Now Make sure sales order Message type BA00 was sent. in VA03 Goto Extras > Output > Header > Edit.

Step6. In Transaction WE02 Check Outbound IDoc status of Message type ORDRSP.

/wp-content/uploads/2013/08/25_266448.jpg

Here Idoc 911047 as shown above. If it is successfully processed it will have status 3.


Step7: Then Check Inbound IDoc of Message type ORDRSP. Here the IDoc 911048. If it is successfully processed and have status 53 then check information message saying purchasing doc XXX successfully processed as shown below.

/wp-content/uploads/2013/08/30_266468.jpg

Step8: Now Display the purchase order in ME23N and in item confirmations tab observe the sales order number is updated with confirmed schedule line as shown below.

/wp-content/uploads/2013/08/31_266469.jpg

-End Of Document Part1

In Continuation of this document I will explain about ‘processing delivery in SD and goods receipt in MM for the above business process using IDocs’ in my next document http://scn.sap.com/docs/DOC-45777

Thanks For Reading & Please share your reviews & feedback….

Regards

Satish

Source: https://blogs.sap.com/2013/08/22/integrating-mm-sd-modules-in-same-client-to-create-sales-order-in-supplying-company-code-using-po-raised-in-receiving-company-code-by-i-doc-message-type-orders-part1/