STEPSABIC Transformation through Execution of Projects

STEP 3 - Execute Program or Project

Development SpecificationTemplate Version 1.0

Debagging process and differences for debagging in WH

[EP_LE_EXXXX]

Process: Warehouse Sales order processing Reseller[FANAR +][Project ID][Project Manager][SBU Name]

Table of Contents1 Business Requirement........................................................................................4

1.1 Functional description..................................................................................................41.2 Scope...........................................................................................................................41.3 Reason for development..............................................................................................5

1.3.1 Description of alternative.......................................................................................51.3.2 Reason why alternative is not acceptable.............................................................5

1.4 Authorisation................................................................................................................51.5 Risk analysis................................................................................................................51.6 Test cases...................................................................................................................51.7 Program Type..............................................................................................................5

2 Development Specification.................................................................................62.1 Configuration and other pre-conditions........................................................................62.2 Menu path....................................................................................................................62.3 Processing logic...........................................................................................................62.4 Enhancements.............................................................................................................62.5 BADI’s..........................................................................................................................62.6 User exits.....................................................................................................................62.7 Customer programs.....................................................................................................72.8 User Interface (UI).......................................................................................................7

2.8.1 Screens.................................................................................................................72.8.2 Form......................................................................................................................72.8.3 Report....................................................................................................................72.8.4 Webdynpro for ABAP / JAVA................................................................................7

2.9 Interface.......................................................................................................................72.9.1 SAP PI...................................................................................................................7

2.10 Data model...............................................................................................................72.11 Jobs..........................................................................................................................72.12 Portal Content...........................................................................................................72.13 Workflow...................................................................................................................72.14 Result of Test case...................................................................................................7

Version HistoryVersion Author Date Description1.0 Ronen Madar 25-Nov-2014 Initial

1 Business Requirement

The business requirements for this change are as follow:

To be able settle the stock differences and financial activities with the affiliate.

To be able to debag stock for customer sales.

SABIC should not degage materials using raw materials from different affiliates for the same order.

1.1 Functional description

SABIC EP want to be able to do debag the material they sale to the customer.

Today SABIC EP use production order in order to degage the stock if the customer will require so.

As soon as production order is released a transfer requirements will be created to facilitate the picking solution required by

SABIC.

The picking process will involve a user exits to make sure that raw materials of the manufacturing batch will not be picked

from more than one affiliate to comply with the NBB agreements.

A service purchase order will be used to collect the debagging cost.

1.2 ScopeBelow you can see the future proposed process for SABIC EP.

Test scenario:1. Create sales order for customer based on customer purchase order.2. Create outbound delivery for sales order.3. Create shipment for sales order outbound delivery.4. Create an STO with reference to the sales order from the WH to the SPC plant.5. Create a production order with reference to the sales order for the debagging process. 6. Create Transfer requirements for the production order picking.7. Create Transfer order for the components picking for the debagging process.8. Run picking process using User Exit to avoid pick of one MFB from more than one affiliate.9. Change shipment status to check in to check if the stock has been stages to the supply area in the WH.

And execute the debagging process in the supply area and convert the component to the FG and transfer the stock to special stock for the sales order as well as finding the NBB’s for each MFB’s. NEW UPDATE PROGRAM.

10.Close the production order with TECO- NEW UPDATE PROGRAM11.UPDATE SASP OF THE MATERIAL CHANGES USING MVT 412E INSTEAD OF 261 AND 101-NEW UPDATE PROGRAM12.Crate outbound delivery for the STO in the WH.13.Create Transfer order for the STO outbound delivery in the WH.14.Confirm picking of FG in the WH.15.Star actual loading to the truck in the WH.16.Change shipment status to loading end call differences procedure – NEW UPDATE PROGRAM 17.Change shipment status to completion and post GI from WH for STO – NEW UPDATE PROGRAM 18.Trigger service purchase order for Debagging cost collection. – NEW UPDATE PROGRAM.19.Post GR in SPC plant for the STO outbound delivery automatically when posting GI from the WH.20. Update sales order outbound delivery with the NBB’s picked in the WH and the actual quantity-NEW UPDATE PROGRAM20. Create Transfer order for the sales order outbound delivery in SPC for the NBB received- NEW PROGRAM IF PICKING TO BE DONE AUTHOMATICALLY. 20.Change shipment completion status to post GI automatically for the sales order from SPC to customer.21.Post GI for sales order outbound delivery.

Test Data:

1. Available stock in the warehouse as of 30.04.2014 from MFG1 from SHARK 30 TON -> NBB1-6000705504AFF1 - Material 22000051, STO 1M01->1054: 4501607401, STO 1250->1M01; 4501607402 OBD 1250-1M01: 85491007 DONE, INB 1M01: 5012228724OBD 1M01-1054: 85491016 DONE, INB 1054 80064256, MAT DOC: 5012228729, conversion NBB->MFB 49157422271250- MFB : 00015013581M01-NBB: 60007055041054-NBB: 6000705504

Conversion back to MFB Document 4915742227 posted

2. Manufacturing batch from number MFG1 from SHARK 90 TON -> NBB2 -6000705505AFF1 - Material 22000051, STO 1M01->1054: 4501607401, STO 1250->1M01; 4501607402 OBD 1250-1M01: 85491008 DONE, INB 1M01: 5012228725OBD 1M01-1054: 85491017 DONE, INB 1054: 180064256, MAT DOC: 5012228728, conversion NBB->MFB 49157422281250- MFB: 00015013591M01-NBB: 60007055051054-NBB: 6000705505

Conversion back to MFB Document 4915742228 posted

3. Manufacturing batch from number MFG1 from PETROKYMIA 65 TON -> NBB2- GR date 12/05/2014.Stock creation could not be executed due to SD condition record error.

AFF2 - Material 22000051, STO 1M07->1054: 4501607405, STO 2050->1M07; 4501607408OBD 2050-1M07: 85491010 POST GIOBD 1M07-1054: 85491014 INB to 1054 1800642601250- MFB: 00015013591M01-NBB :1054- NBB:INB 1054: MAT DOC :

4. Sales order 1, quantity 60 TON and has shortage of 15 KG as a result of the debagging process.UNIT TEST SO: 1073713 quantities 10 TON, STO 4501607412

5. Sales order 2, quantity 120 TON and has surplus of 20 KG as a result of the debagging process.UNIT TEST SO: 1073712 quantities 10 TON, STO 4501607411

Picking for debagging order• Some customers need Bulk instead of packed. Sometimes SABIC has only packed on stock. During sales order

creation, the stock is checked with packed material. A production order is used to debag the required materials.• At the HUB, debagging takes place. Packed material must be picked in SAP; bulk is received automatically in SAP.

This bulk stock is assigned to the customer order.• With the information on the purchase order / production order the packed material can be picked• Procedures

Choose from the SAP Easy Access menu: Logistics -> Logistics Execution -> Internal Whse Processes -> Transfer Requirement -> Display ->

LB13 –> By Requirement

We have created a sales order: 1073713

We have created STO: 4501607412

We have created a production order: 1494466 release the production order and create services order automatically at this stage using function module: BAPI_PO_CREATE1.

Coordinate with the MM team as they will have another specification to explain what data need to be on the services order.

We have created a transfer requirement: 1494466

Enter the warehouse number, requirement type (P) and the production order:

Transfer requirements have been created for the production order components picking.

Select the item and choose the button An overview of the transfer requirement appears where we can see where the stock should be staged into.

The stock that can be picked is listed (sorted) on FIFO base (batch creation date)

Select the first item and choose the calculation buttonNote: it is only allowed to pick from one affiliate

After the picking the transfer order is automatically printed and confirmed. The warehouse operator can use the print out to process the physical picking. In the next step we will trigger the debagging program by clicking on the shipment check in button: since the organizational structure has been changed we will maintain a shipment for the sales order on the SPC mirror plants and not in the WH.

Shipment check inVia the Dispatch advice and the web portal the HUB and Haulier the service providers will be informed to deliver goods to the customer.The haulier arrives at the HUB and checks in with shipment documents. The administrative check in and the registration of the truck id is done in the SAP system.

Procedures:Choose via the Easy Access menu:Logistics->Logistics Execution->Outbound Process->Goods Issue for Outbound Delivery->Shipment->Change->VT02N – Single Documents

Enter the shipment number and click enter

The following screen appears:

Choose the check in button A dialog box appears with special remarks like special requirements Pick/ Pack instruction, Remarks Loading document and

Remarks Distribution Officer Read, if present, the special remarks and Choose Enter A dialog box appears with the actual date check in and time and for entering the Truck id Enter the Truck id (field External ID 1)

Choose the button After a while the message appears in the status bar Save the shipment

Now we want to find the NBB for each one of the MFB picked to the staging area for the debagging process.

The results table will be displayed.

The MSEG-CHARG for the search is our NBB. Remember this batch number

Note: there could be many production batches linked to many Net back batches. We need conversion for each one of the MFB used.

Search criteria to find NBB when transfer order is confirmed to the production staging area: here we trigger conversion program from MFB to NBBTake the plant-LTAP-WERKSStorage location-LTAP-LGORTMaterial-LTAP-MATNRManufacturing batches –LTAP-CHARGIf there are more than one line item on the transfer order LTAP-TAPOS repeat the search for the NBB for each item.Destination bin-LTAP_NLPLA-production order number

Now in production order find the NBB by looking on table MSEG and do the following:MSEG-BWART=311MSEG-MATNR= LTAP-MATNRMSEG- UMMAT= LTAP-MATNRMSEG- WERKS= LTAP-WERKSMSEG- UMWRK= LTAP-WERKSMSEG- UMCHA= LTAP-CHARGEnter selection criteria as per below screen.

NOW, Go to MIGO FM BAPI_GOODSMVT_CREATE to perform movement type 412E to do the following:The import parameters for this FM are as follow:Plant: = the plant we use for the transfer order.Source SL = the storage location from the transfer order.Movement type- BWART = 412EIssuing SL - UMLGO = the transfer order storage location.sales order - MAT_KDAUF = Take the production order from the transfer order LTAP_NLPLA which is the destination bin for the Transfer order and go to table AFPO and take KDAUF when AFPO-AUFNR= LTAP_NLPLA .Sales order line item=AFPO-KDPOSIssuing material MSEG-UMMAT= LTAP-MATNRReceiving Material number- MSEG-MATNR = AFKO-MATNR where AFKO-AUFNR= LTAP_NLPLAQuantity- MSEG-ERFMG= AFKO-GAMNG where AFKO-AUFNR= LTAP_NLPLA

Issuing batch- MSEG-UMCHA= LTAP-CHARGReceiving batch-MSEG-CHARG= is the NBB we found on the previous step.Receiving SL-AFPO-LGORT where AFPO-AUFNR= LTAP_NLPLA

Now you will see the material document created with 412E which includes the MFB to NBB conversion. Material Document 4915742229, the stock is now ready with NBB and FG material number in production area or debagging area.

Stock overview:

NOW WE NEED TO UPDATE SASP OF THE MATERIAL CHANGES USING MVT 412E INSTEAD OF 261 AND 101-NEW UPDATE PROGRAM

Now, As soon as material document is posted with 412E we need to close the production order using transaction code CO02 FM: BAPI_PRODORD_COMPLETE_TECH

Now the stock is ready to be picked and shipped to mirror against STO.

Create outbound for STO: 4501607412

Pick the NBB we have created from the MFB in the debagging process area.

Now we start with the actual load.

Change shipment status to loading end call differences procedure – NEW UPDATE PROGRAM

Check if we can use loading start insteads of the loading end???Start differences calculation for MFB and NBB

Now we create the transfer order for the FG outbound delivery of the STO.

An overview with the transfer order items appearsEnter the actual loaded quantity and the difference indicator 2 when the silo is not empty.If the silo is empty the difference indicator should be S.

Used with another transfer order. Missed this step.1.

After the picking the transfer order to the bay has to be confirmed. With the confirmation it is possible to confirm less or more goods than provided for in the transfer order.Procedures

Choose via the Easy Access menu:Logistics -> Logistics Execution -> Internal Wshe Processes -> Stock Transfer -> Confirm Transfer Order -> Single Document -> LT12 -> In One StepEnter the transfer order number and Warehouse number to confirm.

IF the physical picked quantity for packed goods is equal to the planned debag quantity (picked quantity), the transfer order can be saved If the physical picked quantity is not equal to the picked quantity, enter the actual picked quantity and a difference indicator The transfer order can be savedIf there is a difference a dialog box appears. Choose the button Confirm differenceThe transfer order is confirmed

Picking ConfirmationIf the material is completely loaded, the picking (transfer order) must be confirmed. The actual quantity is measured with the Weighbridge.If there were a debag difference, you can post the difference quantity to storage type for differences.

The differences will be posted to storage type 999 with link to the transfer order automatically.

We now have the differences in NBB in storage type 999.

As soon as we confirm the transfer order for the STO outbound delivery we will post GI automatically. This will be done by standard configuration.

Change shipment status to complete to post GI for the sales order.

Reason for developmentTo comply with the Net back process requirements to avoid posting debagging consumption to SABIC HQ PNL accounts.

1.2.1 Description of alternativeUse production order and modify the way we report the cost.

1.2.2 Reason why alternative is not acceptableNo compliant with the netback accounts reporting strategy.

1.3 AuthorisationUser will need to have access to the following:

Display sales order.

Display planned order.

Create purchase service order.

Create WM transfer requirements.

Create WM transfer order.

Create IM material document.

1.4 Risk analysisNone

1.5 Test cases

Step # Description Expected results Actual results

1.6 Program Type

Choose the correct program type:

Enhancement BADI Customer Program User Exit

Data model Report UI Other

2 Development Specification

Change shipment status to check in to check if the stock has been stages to the supply area in the WH.And execute the debagging process in the supply area and convert the component to the FG and transfer the stock to special stock for the sales order as well as finding the NBB’s for each MFB’s. NEW UPDATE PROGRAM.

Close the production order with TECO- NEW UPDATE PROGRAM UPDATE SASP OF THE MATERIAL CHANGES USING MVT 412E INSTEAD OF 261 AND 101-NEW UPDATE

PROGRAM Change shipment status to loading end call differences procedure – NEW UPDATE PROGRAM Change shipment status to completion and post GI from WH for STO – NEW UPDATE PROGRAM Trigger service purchase order for Debagging cost collection. – NEW UPDATE PROGRAM. Update sales order outbound delivery with the NBB’s picked in the WH and the actual quantity-NEW UPDATE

PROGRAM 20. Create Transfer order for the sales order outbound delivery in SPC for the NBB received- NEW PROGRAM IF

PICKING TO BE DONE AUTHOMATICALLY.

2.1 Configuration and other pre-conditions

IM movement type 412E should trigger WM movement type to convert the stock in WM.

2.2 Menu pathN/A

2.3 Processing logic

Business process step by step:1. Customer sends a purchase order. This request is registered as a sales order in the selling company;2. Together with the creation of the sales order, a production order for the debag operation is created;3. Optionally the Customer Service Officer will prepare the production order: assign specific component batches, receiving

batches, additional notes in the activity description etc. This will be done exceptionally. Most debag orders will be executed without manual interruption;

4. When the sales document is relevant for delivery, a delivery document is created via a batch job.5. Based on the deliveries shipments are created. By setting the status planning the Hub will be informed to arrange transport for a

specific shipment;6. Via the ALTR-output type (Shipment call-off) the Hub or haulier is informed and notified to arrange transport for a specific

shipment. Details like destination, dates, quantity, and material are listed in the document. Texts (additional requirements) can be used to give extra information like output-instructions;

7. Based on the ALTR the HUB or haulier arranges transport;8. One or two days before delivery date, the production order will be released automatically by Customer Service Officer;9. Purchase orders for the service will be created automatically for released production order;10.The purchase order, inclusive instructions, is send to the service provider/HUB. The purchase order also contains the

components that have been picked in step 12. The HUB receives only one document. The WM picking documents in step 13 are no longer necessary;

11.Production orders that have been released are relevant for staging (creating WM transfer requirements) component materials. Staging is done automatically via release of production order;

12.WM transfer orders for picking component materials are created automatically during release of production order;13.Transfer orders for component materials are used to trigger picking in HUB;14. In HUB physical picking of component materials is done;16.Haulier arrives at HUB and checks in with shipment documents;

23.The Hub executes the physical picking and loading;24.After physical picking a confirmation of the loaded weight is made; 29.Haulier checks out at HUB;30.The Hub is responsible for creation of transport documents like CMR / certificates / etc. Quality certificate and customs invoice

have been created in SABIC EPC system (step 28). CMR will be made by HUB without support from SABIC EPC system;

25.A confirmation from the HUB is carried over to the SABIC EPC system. The confirmation contains 2 parts: the normal confirmation of a delivery via the overview of dispatch advises, and the realized quantities for the production order containing the batches and quantities issued for the debag operation;

15.Results of the picking of component materials is confirmed in the SABIC EPC system by the back-office employee;17.Administrative check-in is done in SABIC EPC system by back-office employee18.Based on the administrative check-in (step 17) the goods issue of component materials that have been confirmed for picking

(step 12), is posted. These postings trigger a material to material transfer posting for SABIC HQ system;19.Also via the administrative check-in (step 17) a goods receipt for the production order is done automatically. The receiving batch

is set to the largest component batch issued in step 18).20.Back-office employee creates a WM picking order for delivery; 21.Optionally: After picking the back-office employee changes the status of the shipment document(s) into “loading started”. The

‘loading list’ (step 22) is no longer needed because loading has already been done;26.The HUB employee enters the loaded quantities as confirmation to the WM picking order for delivery in SAP;27.Optionally: After administrative picking for delivery has been confirmed, the shipment is set to status ‘end loading’ in the SABIC

EPC system by back-office employee;28.No documents will be printed from SABIC EPC system; 29.Haulier checks out at HUB;30.The Hub is responsible for creation of transport documents like CMR / certificates / etc. Quality certificate and customs invoice

have been created in SABIC EPC system (step 28). CMR will be made by HUB without support from SABIC EPC system;

31.Setting shipment to status ‘loading ended’ also triggers the goods issue posting;32.The difference between the quantity posted goods issue for delivery and realized goods receipt for the production order is

corrected automatically to the production order;33.The HUB employee creates WM transfer orders for remaining component materials to bring them back to the warehouse;34.The corrections to the component materials are posted as correction to the production order. These corrections are posted as a

material to material transfer to SABIC HQ system;35.Goods receipts for the purchase orders for the service is posted automatically based on the received quantities for the

production order;36.The production order will be ‘closed’. The balance of issued packed materials and received bulk material is calculated and

transferred to the SABIC HQ system as a difference for additional activities (movement type 911/961);37.The HUB creates an invoice for the services;38.An invoice for the services is send to SABIC EPC;39. Invoice for additional activities is posted, and available for netback;40.Finally an invoice is created for all deliveries posted goods issue.

2.4 Enhancements

2.5 BADI’s

ZBI_DEBAGG - Trigger debagging process from shipment

Definition name - BADI_LE_SHIPMENTMethod - BEFORE_UPDATE – call below debagging FMs

Z_DEBAGGING_CHKIN Z_DEBAGGING_LDING_STRT Z_DEBAGGING_LDING_END

2.6 User exits

2.7 Customer programsFunction group - Z_DEBAGGINGFunction modules –

Z_DEBAGGING_CHAR_UPD – This Function module is used to copy characteristics data from one Batch to anothero Import parameterso Source materialo Target materialo Plant o Batch

Use FM CLAF_CLASSIFICATION_OF_OBJECTS to read classification data for source material, plant and batch for class Z_GEN.

Read classification data for below characteristics Z_GEN_STONR Z_GEN_STOITM Z_GEN_MFTAFFIL Z_GEN_BOLDAT

Use FM BAPI_OBJCL_CHANG to copy value for above characteristics to target material, plant and batch where class type = ‘022’

Z_DEBAGGING_CHKINo Call FM Z_DEBAGGING_CHK_DEBAG2 to check if it is relevant to debaggingo If yes, then get sales order number and item number from the delivery detailso Get production order details returned from above FMo Select transfer order for production order

Select from table LTAP where SONUM is initial and NLPLA = production order number selected above Check if TO is confirmed from table LTAK where KQUIT = ‘X’. if yes

o Get MFB from the transfer order and select corresponding NBB from MSEG table where movement type is 309.o For each line selected in transfer order

Check if NBB batch exist for the finished material and plant. If not, select valuation type from component MFG batch and pass it to finished material NBB batch

call FM VB_CREATE_BATCH to create the batch Call FM BAPI_GOODSMVT_CREATE to create material document with movement type 412 special indicator E to move

stock from component material MFG batch to finished material NBB batch. Call FM Z_DEBAGGING_CHAR_UPD to copy characteristics from component NBB batch to finished material NBB

batch. Call FM Z_DEBAGGING_SERVICE to create service entry sheet. Select data from table LUBU to check if the TO has been created for the Posting change generated by the material

document above. If not then Use FM L_TO_CREATE_POSTING_CHANGE to cerate TO for posting change generated by above material

document. Call FM BAPI_PRODORD_COMPLETE_TECH to mark production order ‘Technically Complete’. Z_DEBAGGING_CHK_DEBAG2

o This FM is used to check if transaction is relevant to debagging. Import parameters - Delivery items in table VTRLP_TAB Export parameters – Debagging flag and AFPO table with production order details where production order is already

technically complete. Get sales order number and item from delivery details table Select STO details from EKKN table for sales order and item selected above Get outbound delivery for the STO selected above from table EKBE. Select delivery details for the table selected above from the table LIPS. Get plant for the delivery selected above Select data from table ZMFB_NBB for plant selected above. If field Debag in the table is set to X, set debagging flag.

Z_DEBAGGING_CHK_DEBAGo This FM is used to check if transaction is relevant to debagging.

Import parameters - Delivery items in table VTRLP_TAB Export parameters – Debagging flag and AFPO table with production order details where production order is not

technically complete. Get sales order number and item from delivery details table Select production order details from AFPO table for sales order and item selected above Get plant from the production order Select data from table ZMFB_NBB for plant selected above.

If field Debag in the table is set to X, set debagging flag. Z_DEBAGGING_CREATE_TO

o This FM is used to call BDC for LT03 to create transfer order.

Z_DEBAGGING_LDING_END – This FM is used to post material documents if STO OBD TO is confirmed with differences. DEBAGGING_LDING_STRT – This FM is used to create transfer order for STO OBD.

o Call FM Z_DEBAGGING_CHK_DEBAG2 to check if it is relevant to debaggingo If yes, then get sales order number and item number from the delivery detailso Get production order details returned from above FMo Get STO for the sales order from table EKKNo Get delivery for the STO from table LIPSo Get warehouse number for the delivery from table LIKPo Get transfer order details from table LTAPo Check if difference quantity is not 0.o if difference quantity is less than 0,

Use FM BAPI_GOODSMVT_CREATE with code ‘04’ to post a material document with movement type 313 and special stock indicator E and storage location 1083 for difference quantity.

Use FM BAPI_GOODSMVT_CREATE with code ‘04’ to post a material document with movement type 315 and special stock indicator E and storage location 1083 for difference quantity.

o If difference quantity is more than 0. Use FM BAPI_GOODSMVT_CREATE with code ‘03’ to post a material document with movement type 962 for the

difference quantity to move quantity to storage location 1083. Z_DEBAGGING_LDING_STRT – This FM is used to create transfer order for STO OBD.

o Call FM Z_DEBAGGING_CHK_DEBAG2 to check if it is relevant to debaggingo If yes, then get sales order number and item number from the delivery detailso Get production order details returned from above FMo Get STO for the sales order from table EKKNo Get delivery for the STO from table LIPSo Get warehouse number for the delivery from table LIKPo Check if transfer order already created by checking delivery pick status in table VBUK for above delivery. check if KOSTK is ‘A’.o Select transfer order for production order

Select from table LTAP where SONUM is initial and NLPLA = production order number selected aboveo Get MFB from the transfer order and select corresponding NBB from MSEG tableo Call FM L_TO_CREATE_DN to create transfer order for OBD with batch selected above

Z_DEBAGGING_SERVICE – This FM is used to select relevant data and pass on to FM Z_DEBAGGING_SERVICE_CREATE to create service entry sheet.

o Import parameters

Sales order Sales order item Plant Quantity Unit Material Batch

Select plant vendor from table ZDEBAGVENDOR for the Plant Select all framework order for the vendor selected above from table EKKO (document type FO) Filter orders selected above to find only open orders. Select order details from EKPO for all entries selected

above where ELIKZ is initial. Sort selected orders and pick the latest one and get PACKNO from the order. Use PACKNO selected above to get service detail from table ESLL Pass all relevant data to FM Z_DEBAGGING_SERVICE_CREATE to create service entry sheet.

Z_DEBAGGING_SERVICE_CREATE o This FM is used to call BDC for ML81 to create service entry sheet.

2.8 User Interface (UI)N/A

2.8.1 ScreensN/A

2.8.2 FormN/A

2.8.3 ReportN/A

2.8.4 Webdynpro for ABAP / JAVAN/A

2.9 Interface

2.9.1 SAP PIN/A

2.10Data modelN/A

2.11JobsN/A

2.12Portal ContentN/A

2.13Workflow N/A

2.14Result of Test case Pl. capture the results of the test cases defined in 1.6 above.