Routings and Work Centers Transfer using ALE

Can anbody has written inbound function modules
for Routing and Workcenters using message types
LOIROU and LOIWCS using ALE Transaction POIM
High points will be rewarded.

Hi,
Check the FM for routing
IDOC_INPUT_ROUTING_CREATE .
Regards,
Sharath

Similar Messages

I updated to yosemite and now if someone is using imessage and sends a text message to my phone it doesn't show up on my phone but does on my computer. I don't want messages on my computer! How do I get this to go away and work like it used to?

I updated to yosemite and now if someone is using imessage and sends a text message to my phone it doesn't show up on my phone but does on my computer. I don't want messages on my computer! How do I get this to go away and work like it used to?

Follow the instructions under the heading "How to unlink a phone number" on this page.

Data transfer using ALE/IDOC into XML.

Dear All,
I have to transfer FI document data (FB01) from the sap system ,convert it into XML and dump it in 1 of the file servers.I want to do this using ALE/IDOC.Is it possible to do the same and how.Similarly i want to do the same for Vendor and Customer master i.e sending the data in XML format.
Kindly Suggest how do i go about doin the same..Its very urgent.Please help.
Thanks & Regards,
Lailu Philip.

In continuation:
Example Purchasing & Selling scenario
We will develop a custom IDoc to carry the billing number from the Service Receivers system to the Service Providers system. We will populate the IDoc in a user exit on the sending side and we will process the transaction on the receiving side using a custom function module and a BDC transaction call.
No rule conversion, segment filtering or version conversion will be implemented in the model as described in Figure 1.
Requirements
Working ALE environment - See ALE Basis Configuration Guide;
ALE scenario design together with the business requirement;
Development access; and
ALE configuration access.
NOTES:
1. All IMG references to transactions are located in the transaction SALE which is the ALE portion of the IMG
2. This is one way of developing a scenario where no message control exists. If message control exist (EG. On purchase orders) then NAST can be used to call an outbound function module that would create the required IDocs.
3. Extensive knowledge of IDocs and ALE basis configuration is required in order to understand this guide.
2. OUTBOUND PROCESSING
2.1. Create IDoc type (WE30) Client independent
The IDoc type refers to the IDoc structure that you will require for your development. In our case the IDoc type is called ZINVRV01. This IDoc type will have 1 segment called Z1INVRV with 2 fields, LIFNR & XBLNR, in this segment. If you require many segments or nested segments then they are also created using the same procedure.
We will create the IDoc of the following structure:
ZINVRV01
Purchasing and Selling - Invoice receipt reversal
Z1INVRV P&S - Segment 1
Segment fields
LIFNR Vendor account number
XBLNR Reference document number
Figure 3: IDoc type ZINVRV01
To create the IDoc type, follow these next few steps:
Enter transaction WE30 (ALE -> Extensions -> IDoc types -> Maintain IDoc type)
Type in ZINVRV01 and click on Basic IDoc type, click the Create icon
Click on Create new (we are creating an IDoc from scratch but you may want to copy another IDoc if it is similar to your requirements) and enter a description, and press enter
Click on ZINVRV01 and then on the Create icon
Enter Z1INVRV as the segment type (must start with Z1), check mandatory if the segment must exist (in this case check it), enter 1 in minimum number and 1 as maximum number. (Make the maximum number 9999999999 if there are going to be many of these segments in each IDoc. IE. When line items are passed via IDocs), click on Segment editor
Enter a description for your segment type and create
Enter a description for your segment, enter each field required in your IDoc, in our case type LIFNR across for Field name, DE structure and DE documentation, repeat for XBLNR and press enter to validate.
Save and generate, press back
To release the segment choose Goto, Release from the menu
Check the box on the line of your new segment
Save, back and enter
Your IDoc type structure should be displayed with your new segment
Save and back
To release the IDoc type choose Extras, Release type from the menu and Yes
Your IDoc is now ready for use. If you need to add fields or segments to your IDoc type, you will need to cancel the release of the IDoc type as well as the segment release using a similar procedure followed above (except now you uncheck the release box for the segment and you choose cancel release for the IDoc type).
2.2. Create message type (WE81) Client independent
To create a new message type, follow these next few steps:
Enter transaction WE81 (ALE -> Extensions -> IDoc types -> Maintain message type for intermed. Structure -> Create logical message type)
Choose Create logical message type by double clicking on it
Click on change icon to enter change mode
Click on New entries to add a new type
Enter the required message type, in our case it is ZINVRV and an appropriate description
Save and exit.
Your message type has now been created. The next step will be to link it to the IDoc.
2.2.1. Link message to IDoc type (WE82 & BD69) Client independent
To link the message type to the IDoc type follow these next few steps:
Enter transaction WE82 (ALE -> Extensions -> IDoc types -> Maintain message type for intermed. Structure -> EDI: Message Types and Assignment to IDoc Types)
Click on change icon to enter change mode
Click on New entries to create the link
Enter the message type ZINVRV and the BasicIDoc type as ZINVRV01
Save and exit
Enter transaction BD69 (ALE -> Extensions -> IDoc types -> Maintain message type for intermed. Structure -> Assign message type to IDoc for ALE)
Click on change icon to enter change mode
Click on New entries to create the link
Enter the message type ZINVRV and the BasicIDoc type as ZINVRV01
Save and exit
Your IDoc is now linked to your message type. We still need to link object types and add the message to the model before we can use the message.
2.2.2. Maintain object type for message type (BD59) Client independent
The ALE objects are used to create links between IDocs and applications objects, to control the serialisation, to filter messages in the customer model and to use listings.
For our own message type and IDoc you must maintain object types for the links.
If you want to check the serialisation for the message type, then you must maintain object types for the serialisation. If no serialisation object has been maintained for a given message type, then the serialisation will not be checked for this message type.
To add an object type to our message type, follow these next few steps:
Enter transaction BD59 (ALE -> Extensions -> ALE object maintenance -> Maintain object types)
Type in your message type ZINVRV and press enter
Click on New entries
Enter your object type, LIFNR (We need to use the vendor as a filter object), the segment name where LIFNR resides, Z1INVRV, a number 1 for the sequence followed by the actual field name LIFNR
Save and exit.
You have now created an object that well use as a filter object in the customer model to direct the flow of messages to the various logical systems based on the vendors in the filter of the message type ZINVRV.
We now need to add our new message type to the distribution model.
2.3. Configuring the Distribution Model
This task is performed on your ALE reference client.
2.3.1. Manual Configuration (BD64) Client dependent
To manually configure the customer distribution model, read the ALE configuration procedure, and follow these steps:
Perform the Maintain customer distribution model directly function. (ALE -> Distribution customer model -> Maintain customer distribution model directly)
Specify the customer model you want to maintain and the logical system that is to be the sender of the messages OR create a new model. (Create model ALE with logical system ALELS1C400)
Choose the receiving systems to which the sending system must forward message type ZINVRV to.
For each receiving logical system allocate the message type necessary for communication to the receiving systems as per ALE configuration procedure.
Create filter objects (in our case LIFNR as the object type with the associated vendor number, 0000018001 with leading zeros, in the object area) for the message types.
Save the entries.
NOTES:
You cannot maintain a message type between the same sender and receiver in more than one customer distribution model.
Only the owner is authorised to modify the model.
To change the owner of a model, choose the 'Maintain ownership of customer distribution model' function. Make sure that all changes will be distributed to all systems that know the corresponding model. To do so, you can use the correction and transport system.
To transport the customer distribution model you should use the Distribute customer model function of the IMG as described below.
2.3.2. Distribute customer model (BD71) Client dependent
After the customer model has been created centrally, it must be distributed to the other remote systems. This entails first of all setting up the communication for the distributed systems and then sending the model.
2.3.2.1. Distribute Model (BD71) Client dependent
This task is performed on your ALE reference client. To distribute the customer distribution model, read the ALE configuration procedure and follow these steps:
Make the settings for the communication with the other decentral systems, you have not set them yet.
Define the RFC destination for R/3 connections whose names correspond to the name of the corresponding logical system.
Create the output partner profile.
Distribute the customer model
Specify the name of the customer model.
You must specify the target system to which you want to distribute the customer model.
You must repeat this function for every distributed logical system.
2.3.2.2. Maintain sending system partner profile (WE20) Client dependent
With this function, you define the partner profiles for all outbound and inbound messages on the basis of the customer distribution model.
After you have defined and distributed the customer model, you will have to maintain the partner profiles locally. To do this read the ALE configuration procedure.
Enter the output mode (background, immediately) and the package size for outbound processing.
Requirements
The customer model must be maintained.
RFC destinations must be maintained.
The customer model must be distributed.
To ensure that the appropriate persons in charge are informed if a processing error occurs, you must make settings in: Error processing Maintain organisational units.
2.4. Populate & distribute IDoc using ABAP
An IDoc consists of a control record with structure edidc and one or more data records with structure edidd. The control record contains the sender and recipient of the IDoc, as well as information on the type of message.
To be able to pass an IDoc to the ALE layer, you must set up a field string with structure edidc and an internal table with structure edidd. They are used to call function module master_idoc_distribute, which performs the save to the database and triggers the dispatch if necessary.
2.4.1. Example code
The code displayed below does the following:
populates our IDoc segment Z1INVR with the 2 fields XBLNR and LIFNR, populates the segment name and appends this to an internal table used to store the IDoc data;
populates the control record info with the message type and IDoc type; and
calls the MASTER_IDOC_DISTRIBUTE function module which distributes the IDoc as configured in the customer distribution model.
Data declaration statements
DATA: C_INVREV_SEGNAME(7) TYPE C VALUE 'Z1INVRV',
C_INVREV_MESTYPE(6) TYPE C VALUE 'ZINVRV',
C_INVREV_IDOC_TYPE(8) TYPE C VALUE 'ZINVRV01',
Z1INVRV LIKE Z1INVRV,
C_INVREV_DOCTYPE LIKE BKPF-BLART VALUE 'YY',
IDOC_CONTROL LIKE EDIDC,
T_COMM_CONTROL LIKE EDIDC OCCURS 0 WITH HEADER LINE,
IDOC_DATA LIKE EDIDD OCCURS 0 WITH HEADER LINE.
Move the document header into a structure
LOOP AT DOC_HEAD_TAB INTO DOC_HEAD.
ENDLOOP.
Move the document item data into a structure
LOOP AT DOC_ITEM_TAB INTO DOC_ITEM WHERE NOT ( LIFNR IS INITIAL ).
ENDLOOP.
Populate the IDoc segments field with the required data
CLEAR Z1INVRV.
Z1INVRV-LIFNR = DOC_ITEM-LIFNR. Store vendor number for filter
Z1INVRV-XBLNR = DOC_HEAD-XBLNR. Billing number
IDOC_DATA-SEGNAM = C_INVREV_SEGNAME. Segment name
IDOC_DATA-SDATA = Z1INVRV. Segment data
APPEND IDOC_DATA. Populate IDoc internal table
Move the control data info required for the distribution
IDOC_CONTROL-MESTYP = C_INVREV_MESTYPE.
IDOC_CONTROL-DOCTYP = C_INVREV_IDOC_TYPE.
Call the distribute function with the required parameters
CALL FUNCTION 'MASTER_IDOC_DISTRIBUTE' IN UPDATE TASK
EXPORTING
MASTER_IDOC_CONTROL = IDOC_CONTROL
TABLES
COMMUNICATION_IDOC_CONTROL = T_COMM_CONTROL
MASTER_IDOC_DATA = IDOC_DATA
EXCEPTIONS
ERROR_IN_IDOC_CONTROL = 1
ERROR_WRITING_IDOC_STATUS = 2
ERROR_IN_IDOC_DATA = 3
SENDING_LOGICAL_SYSTEM_UNKNOWN = 4
OTHERS = 5.
Figure 4: Outbound processing example code
NOTE:
For debugging purposes, use transaction WE05 (IDoc overview) to see check your IDoc status, or to see whether an IDoc was created/
3. INBOUND PROCESSING
3.1. Create Function Module
This function module is called when a message type, of type ZINVRV, comes into the receiving system. This needs to be configured and is dealt with later in this section. The function module is passed the IDoc as a parameter.
Example parameters
Import parameters Reference field Opt Y/N
INPUT_METHOD BDWFAP_PAR-INPUTMETHD N
MASS_PROCESSING BDWFAP_PAR-MASS_PROC N
Export Parameters Reference field Opt Y/N
WORKFLOW_RESULT BDWFAP_PAR-RESULT N
APPLICATION_VARIABLE BDWFAP_PAR-APPL_VAR N
IN_UPDATE_TASK BDWFAP_PAR-UPDATETASK N
CALL_TRANSACTION_DONE BDWFAP_PAR-CALLTRANS N
Table Parameters Reference field Optional Y/N
IDOC_CONTRL EDIDC
IDOC_DATA EDIDD
IDOC_STATUS BDIDOCSTAT
RETURN_VARIABLES BDWFRETVAR
SERIALIZATION_INFO BDI_SER
Exceptions
WRONG_FUNCTION_CALLED
Example code
The code displayed below does the following:
populates a BDC table with the IDoc info;
calls the transaction via a BDC call; and
updates the IDoc status according to the BDC error status.
EXTRACT FROM: Z_IDOC_INPUT_ZINVRV
Declaration of local variables
DATA: C_SEGNAM(10) TYPE C VALUE 'Z1INVRV'.
*-Loop through the IDOCs
LOOP AT IDOC_CONTRL.
*---Loop through the data for the IDOC
LOOP AT IDOC_DATA WHERE DOCNUM = IDOC_CONTRL-DOCNUM.
CASE IDOC_DATA-SEGNAM.
WHEN C_SEGNAM.
Here we get the info from the idoc table
IT_Z1INVRV = IDOC_DATA-SDATA.
ENDCASE.
PERFORM REV_INV.
ENDLOOP.
PERFORM UPDATE_IDOC_STATUS.
ENDLOOP.
FORM REV_INV "Reverse invoice form
Local variables & constants
DATA: C_TCODE LIKE BKPF-TCODE VALUE 'VF11'. "BDC transaction code
Now we can build the bdc table to call the reversal transaction start of screen 109
CLEAR BDC_TAB.
BDC_TAB-PROGRAM = 'SAPMV60A'.
BDC_TAB-DYNPRO = '109'.
BDC_TAB-DYNBEGIN = 'X'.
APPEND BDC_TAB.
Document number
CLEAR BDC_TAB.
BDC_TAB-FNAM = 'KOMFK-VBELN(01)'.
BDC_TAB-FVAL = IT_Z1INVRV-XBLNR. "Billing document number
APPEND BDC_TAB.
OK Code for screen 109
CLEAR BDC_TAB.
BDC_TAB-FNAM = 'BDC_OKCODE'.
BDC_TAB-FVAL = 'SICH'.
APPEND BDC_TAB.
Now we can call transaction 'VF11' with the populated bdc table. The transaction is called inside the idoc-contrl loop, so a transaction will be called for every idoc (journal). the transaction is called in no-display mode ('N') because this code runs in background as it is called by ale. The update is specified to be synchronous ('S') because we have to wait for the result to update the idoc status correctly.
CALL TRANSACTION C_TCODE USING BDC_TAB MODE 'N' UPDATE 'S'.
Store the return code for use in another form (status update)
RETURN_CODE = SY-SUBRC.
Here we check the return code, if there was an error, we put the transaction in a bdc session for the user to review and correct.
IF SY-SUBRC NE 0.
CALL FUNCTION 'BDC_OPEN_GROUP'
EXPORTING
CLIENT = SY-MANDT
GROUP = 'ZINVRV'
USER = C_ALE_USER
KEEP = 'X'.
CALL FUNCTION 'BDC_INSERT'
EXPORTING
TCODE = C_TCODE
TABLES
DYNPROTAB = BDC_TAB.
CALL FUNCTION 'BDC_CLOSE_GROUP'
EXCEPTIONS
NOT_OPEN = 1
QUEUE_ERROR = 2
OTHERS = 3.
ELSE. "No problems
C_EXISTS = 'N'.
Select from the billing document table to get sales doc number
SELECT * FROM VBRP WHERE VBELN = IT_Z1INVRV-XBLNR.
Select from the sales document table to get user status number
SELECT SINGLE * FROM VBAP WHERE VBELN = VBRP-AUBEL AND
POSNR = VBRP-AUPOS.
Select from the status table to change the user status to pending
SELECT * FROM JEST WHERE OBJNR = VBAP-OBJNR AND
STAT LIKE C_USER_STATUS.
IF JEST-STAT = C_US_PENDING. "User status is pending
JEST-INACT = C_UNCHECKED. "Make pending the active status
UPDATE JEST.
C_EXISTS = 'Y'. "I.E. An entry is already in table
ELSEIF JEST-INACT = C_UNCHECKED AND JEST-STAT NE C_US_PENDING.
JEST-INACT = C_CHECKED. "Make everything else inactive
UPDATE JEST.
ENDIF.
ENDSELECT.
IF C_EXISTS = 'N'. "I.E. Pending has never been a status before
JEST-OBJNR = VBAP-OBJNR.
JEST-STAT = C_US_PENDING.
JEST-INACT = C_UNCHECKED. "Make pending the active status
INSERT JEST.
ENDIF.
ENDSELECT. "Select from VBRP (Billing document table)
ENDIF.
ENDFORM. " REV_INV
FORM UPDATE_IDOC_STATUS.
Now we check the CALL TRANSACTION return code and set IDOC status
CLEAR IDOC_STATUS.
IF RETURN_CODE = 0.
WORKFLOW_RESULT = '0'.
IDOC_STATUS-DOCNUM = IDOC_CONTRL-DOCNUM.
IDOC_STATUS-STATUS = '53'.
IDOC_STATUS-UNAME = SY-UNAME.
IDOC_STATUS-REPID = SY-REPID.
IDOC_STATUS-MSGTY = SY-MSGTY.
IDOC_STATUS-MSGID = SY-MSGID.
IDOC_STATUS-MSGNO = SY-MSGNO.
IDOC_STATUS-MSGV1 = SY-MSGV1.
IDOC_STATUS-MSGV2 = SY-MSGV2.
IDOC_STATUS-MSGV3 = SY-MSGV3.
IDOC_STATUS-MSGV4 = SY-MSGV4.
RETURN_VARIABLES-WF_PARAM = 'Processed_IDOCs'.
RETURN_VARIABLES-DOC_NUMBER = IDOC_CONTRL-DOCNUM.
APPEND RETURN_VARIABLES.
ELSE.
WORKFLOW_RESULT = '99999'.
IDOC_STATUS-DOCNUM = IDOC_CONTRL-DOCNUM.
IDOC_STATUS-STATUS = '51'.
IDOC_STATUS-UNAME = SY-UNAME.
IDOC_STATUS-REPID = SY-REPID.
IDOC_STATUS-MSGTY = SY-MSGTY.
IDOC_STATUS-MSGID = SY-MSGID.
IDOC_STATUS-MSGNO = SY-MSGNO.
IDOC_STATUS-MSGV1 = SY-MSGV1.
IDOC_STATUS-MSGV2 = SY-MSGV2.
IDOC_STATUS-MSGV3 = SY-MSGV3.
IDOC_STATUS-MSGV4 = SY-MSGV4.
RETURN_VARIABLES-WF_PARAM = 'ERROR_IDOCS'.
RETURN_VARIABLES-DOC_NUMBER = IDOC_CONTRL-DOCNUM.
APPEND RETURN_VARIABLES.
ENDIF.
APPEND IDOC_STATUS.
ENDFORM. " UPDATE_IDOC_STATUS
Figure 5: Inbound processing example code
3.1.1. Debugging inbound FM
Use transaction WE19 to test inbound function module in debugging mode. Also use WE05 to view the IDocs and their statuses.
3.2. Maintain ALE attributes
The inbound function module needs to be linked to the message type and the message type needs to be linked to the appropriate inbound process code at the partner profile level before the scenario is enabled. These steps are described below in detail.
3.2.1. Link Message Type to Function Module (WE57) Client independent
To link a message (ZINVRV) type to a function module (Z_IDOC_INPUT_ZINVRV) follow these steps:
Enter transaction WE57 (ALE -> Extensions -> Inbound -> Allocate function module to logical message)
Select an entry (EG. IDOC_INPUT_ORDERS) and copy
Type in module name Z_IDOC_INPUT_ZINVRV
Type in basic IDoc type as ZINVRV01
Type in message type as ZINVRV
Type object type as IDOCINVOIC (Invoice document) - Used for workflow
Direction should be set to 2 for inbound
Enter and save
3.2.2. Define FM settings (BD51) Client independent
Enter transaction BD51 (ALE -> Extensions -> Inbound -> Define settings for input modules)
Click on New entries
Type in the name of the new function module Z_IDOC_INPUT_ZINVRV
Enter 0 for mass processing in the output column
Save and Exit
3.2.3. Maintain process codes (WE42) Client dependent
A process code needs to be maintained on each client. It then needs to be linked to the message via the partner profiles on each client. This allows the various clients to use a unique function module for the same message type.
To maintain the process code follow these steps:
Log on to the appropriate receiving system client
Execute WE42 (ALE -> Extensions -> Inbound -> Maintaining process codes inbound)
Choose Inbound with ALE service
Choose Processing with function module
Click on Processing with function module and choose create icon
Click on New Entries
Type in process code ZINR and give it a description and save
Now you are asked to Please maintain codes added in ALE entry methods, enter and choose Z_IDOC_INPUT_FIRVSL and copy it. You should choose a FM similar to your one.
Enter your process code ZINR
Enter your function module Z_IDOC_INPUT_ZINVRV
NOTE: The next 6 steps are used in workflow error handling.
Enter IDPKFIDCMT in object type
Enter MASSINPUTFINISHED in End event
Enter IDOCINVOIC in IDoc object type
Enter INPUTERROROCCURREDFI in IDoc start event
Enter INPUTFINISHEDFI in IDoc End event
Enter IDOCINVOIC in Application object type
You will need to determine the task associated with object IDOCINVOIC, and then assign the appropriate position to it. This position will then receive the application error messages via workflow.
To set up the workflow area please consult the Workflow config guide.
3.3. Create inbound partner profile
For each message type you need to maintain the inbound partner profiles.
3.3.1. Maintain receiving system partner profile (WE20) Client dependent
To maintain inbound partner profiles read the document ALE configuration procedure:
Add the message type ZINVRV with process code ZINR.
Enter the output mode (background, immediately) for inbound processing and NO message code.
Enter the position S and choose the ALE administrator 50000085. This position will then receive all the technical ALE errors via workflow.
3.4. Test
Once the inbound function module has been debugged the scenario should be ready to test in its entirety. If problems occur, read through the relevant areas of this document to check your configuration or code.
Hope this will help you,
If you want me to explain more, you can give me your email id.
Reward with points incase you are satisfied.
Regards,
Sushama

Usage Only Routings in Work centers in Plant maintenance

Dear Gurus,
My client wanted only one work center and usage only maintenance task list in begining. Now they want to chage to Only Routings usage. I want to know what is it and what impact it will have now if I changed.
Regards,
PMaddi

The Usage field in the work centre only controls which type of task list or routings the work centre can be used in.
In your case, if you use 002, then you will not be able to use that work centre in a task list or order
PeteA

Business Partner Transfer using ALE/IDOCS

Dear Gurus,
I am using S.R.M. 5.0 system. I am encountering scenario of transferring the business partners from S.R.M sytem to C project which is again add-on module provided by SAP. I have created Distribution Model and have assigned the message type BUS1006 (message type for Business Partner). But I am not able to find the transaction to send the data across to CPD system like BD10 is for transferring material in R/3 system.I have also observerd that the dala eleement of the business partner has got change pointer attached to it. I have got two questions.
1. Is the method that I followed is correct to transfer data? I did it by seeing PPT .If yes than what is the t-code to transfer the business partner equivalent to BD10.
2. In case of change pointers begin activated how should I transfer data? if any documentation is there that will be helpful?
Thanks and Regards,
Saurabh Chhatre
Thanks and Regards,
Saurabh Chhatre

Hi Sergio,
When I tried BUPA_SEND , I came across another transaction BUPA_CALL_FU.
This transaction allows us to select function modules that needs to be called for sending the business partner from S.R.M 5.0.Have you got any idea which are the mandatory F.M's that needs to be selected. I am asking this because there are few F.M's which do not exist in the system.
Or have do you have any idea how we can create these F.M's. As these are standard I am thinking it must be done through customization.
Thanks in advance
Thanks and Regards,
Saurabh Chhatre

Data Transfer Using ALE/IDOC

Dear All,
          I have to implement an ALE\IDOC scenario and i am totally new to this.I have a web based software from where i need to pull data into SAP.
           The moment billing takes place in my web based software i have to pull the required data and generate an accounting document number in SAP using transactions FB01 er FB60 and FB70 depending on vendor or customer Invoice which means i need to have my vendor and customer master data in place before this.The IDOC which i would be using is FIDCCP01.My question is:
The web based software can generate both an XML and EDI file into a domain from where SAP can fetch it. Now,
1. If they can generate an EDI file which format should it be in?
2.If EDI file generation is possible through that web based software its structure should be exactly the same as my IDOC structure right?
3. What would then be the process on SAP side to pick that   EDI file data?
4. Does the transaction WE16 help in picking up an XML file format or an EDI format and convert it automatically into an IDOC and how do we go about it?
5. Now when this idoc is going to generate accounting documents against those billing documents if the customer or vendor does not exist is there a way by which i can first create this vendor\customer in the master and then continue using some other abap tool?
6. Could an email be generated automatically when teh document is posted?
I know these are a lot of questions but i really need an answer to this.
If u have an answer my alternate email id is [email protected]
Awaiting your reply shortly.
Thanks & Regards,
Lailu Philip.

1. XML Format
2. Message type INVOIC01 or INVOIC02 format
3. You need to write a Z program to read data from that path and use FM IDOC_XML_FROM_FILE to convert that XML file to IDOC.
4. Use transaction we60 with above message type it will all help you need. we16 is for testing it could not be used for a solution.
5. In your Z program check before the XML is ubmitted for processing whether the customer exist by select on KNA1 if not use FM BAPI_CUSTOMER_CREATE to create and same for vendor.
6. You need to implement workflow for this.....
Reward points it this helps

How to maintain time spec.of operations in routing and work centers

Dear consultants,
We dont have any time specifications in routing or work center ..
we just create an order and the execution of the production involves many operations....
now we want to be specific about the time of operations as the need is to track the operations.( In the sense which of the operations are delayed).....
How and where should i do these in the routing and workcenters..
Please explain in detail....
Karthick

Hi Karthick,
In your work center in basic data page you maintain std. value key eg: SAP1, this has Setup Machine & Labor fields. In the default values page you specify the unit of measure Eg: HR
Now when you add this work center in your routing operation page, you will find Setup Machine & labor, here you maintain the time required for each of the process.
Now while doing confirmation via co11n, you inform the user to specify the time actually spent on each of the activity. In OPK4 for order type - plant combination you can specify a few defaults such as propose the value etc.
Hope the above is clear.
Regards,
Vivek

WBS transfer using ALE

Hi all,
I'm trying to send complete structure of WBS from FI system to HR system. I have created RFC connection between systems and I've test communication correctly.
I've donde all the steps under "Distribution of Workbreakdown Structure" but I'm not able to Generate Partner Profiles. When I try it I get the message "No messages have been defined for the selection conditions in the model".
Could anyone help?
Thanks in advance and I'm sorry if my english is not quite good.
Delia.

Thank you very much, boby, I already got it, but now I've got another problem. When I send the WBS to my HR system from FI system, my WBS have different code in both systems. May it be a number range?
Does anybody know if it is necesary to customize something to mantain this WBS code equal in both systems?
Thanks in advance!!
Delia.

Send routings to external system using ALE

Hey guys,
I am using ECC 6.0. Under tools->ALE->Master Data Distibution-> Logisitcs-> Bill of Material -> Routings i tried to send a routing to an external system which is already setup for many other types of master data. I get the error "Transaction code /SAPMP/SEROU cannot be executed" . I do not know how to fix it.
I also tried using transaction POIM but did not understand how to send the BOM along with routings and work centers in that T-code. I am able to send materials through that screen successfully but nothing else. If someone could help me out I would appreciate it.
Thanks in Advance.

AN issue regarding " Long Texts "(texts in accounting document).
1) Am using RFBIBL00( Direct Input method ) to transfer Accounting Documents.
2) I need to Update "Texts" both Header & line item for accounting document using Direct input method.
3)I tried to append a custom 'Z' include, that calls SAVE_TEXT function module, in program RFBIBL00 to save texts for the respective Accounting document.But the performance is very low.
4)If I use direct input program /SAPDMC/SAP_LSMW_IMPORT_TEXTS or /SAPDMC/SAP_LSMW_SXDA_TEXTS how will it save texts to document, before it is created , since we are still in LSMW that just generates .CONV file , but it might not create account document number, once the .Conv file goes to RFBIBL00, account document gets generated .
5)another major issue am encountering is , if one of a document fails (error) how about updating texts.How i send text to BDC in this case.
My queries are :
a) Is there any other way to update texts using Direct input method ?
b)Can I integrate, direct input program RSTXLITF with RFBIBL00, is that feasible, will i be able to save texts with out any performance issues ?
I would really appreciate if am given some suggestions or solutions for the above case.
Thanks alot in Advance !

ISSUE:regarding production version tab of MRP4 of data transfer using BD10

Hi all,
This is regarding production version tab of MRP4 of data transfer using ALE idoc (BD10).
When i transfer the data using BD10 the production version is received at receiving end through segment
but not created in MRP4 view tab.An error is coming as-
"You wanted to maintain the master record of the material AB_06.04.09(2). However, it is already being processed by the user EBGABAP and is therefore locked."
I logged in as-EBGABAP
Please help me resolve the issue.
Thanks
Edited by: sanu debu on May 6, 2009 11:08 AM
Edited by: sanu debu on May 6, 2009 11:09 AM
Edited by: sanu debu on May 6, 2009 11:11 AM

>
sanu debu wrote:
> Hi,
> I have to upload production version tab data of MRP4 view(MM01).Please suggest a function moduleor bapi for the same.
>
> Thanks.
>
> Edited by: sanu debu on May 6, 2009 3:24 PM
BAPI_MATERIAL_SAVEDATA can be used, populate the respective fields in input parameter PLANTDATA

Defining CS Work Centers - HR module is not in scope.

Hi Guys,
My client is not using HR module so Technician's personal number assignment to work center is not possible.
So what I have suggested as a work around solution is to create work center with the Technicians Name in the work center description field itself so they know by work center's description which technician is being assigned to a service order.
Say for example Work Center = ZPTech1 = Allan Miller. What do you guy's think of this solution?
Another issue is the client have one service department and this department provides different types of services. For example Inhouse repair, Onsite Service etc.
So they have teams of technicians. One team for Inhouse Repair and another team of technicians for Onsite services. However, there are cases where the technician who belongs to Inhouse repair can also sometimes perform onsite service.
So, since HR module is not in scope and technician's personnel numbers cannot be used to assign to work centers... hence my suggestion was to create work centers as technicians using their names in description field.
However, the problem comes when defining hierarchy.
Say If I create one main work center ZServ = Service Department
Then under ZPServ, if I create two team work centers as Team1 (for Inhouse Repair Team) and Team2 (Onsite Service Team). Then I assign 3 technician work centers viz., TechA, TechB and TechC to team work center Team1 and work centers TechD, TechE and TechF to Team work center Team2 using heirarchy relationship. I think so far it will be fine.
However, say TechA works both in Inhouse repairs and also in Onsite Service. Then I need to assign this technician under both team work centers Team1 and Team2 right? But as far as I know, you cannot have two superior work centers for a particular work center.
So, in this case, what is the best solution?
Instead of creating team workcenters as Team1 and Team2, shall I just create one main work center for Service Department as ZServ then create individual workcenters for each technician? without having a heirarchy structure?
Or say for example if Team1 has cost center 1000 and team2 has cost center 2000, then shall I create two workcenters for the same technician TechA with description as TechA-1000 and TechA-2000. (Then if I have two different workcenters for same technician, with his name and costcenter in the description field then i can assign each workcenter under team1 and team2.
Sorry for the lengthy message... However, I needed to explain the scenario and limitations properly in order to give you a full picture so as to get correct and best suggestions and advice.
Thank you very much for your time and I would really appreciate your inputs.
Best regards,
AR

Hi Suresh,
Answer to first part of your question is: Yes, we are considering employees as vendors and configuring it under Employees (ZEMP) Vendor Account Group.
As you have suggested about Internal Order for employees, somebody else had suggested me with the same.
But I was not convinced why I should go ahead and define internal order for each employees under the Internal Order Type: Employees.
Now could you help me in understanding as to why Internal Orders for each employee, I mean could you tell me the logic behind this, so that I would be in a position to answer if someone asks me.
If there is anymore information / documentation, could you plz forward the same to my mail id, which is: [email protected]
Thank you for your time in replying.
Regards
Sandhya kiran.

Work centers in SAP Solution Manager

Hi!
I have patched my SOLMAN 4.0 to SP 15 and have configured the Work Center functionality.
I have assigned the first Work Center Z_SAP_SMWORK_SETUP, it works.
Now I would like to use the System Monitoring functionality and use this Work Center.
The appropriate role therefor is SAP_SMWORK_SYS_MON.
Unfortunately this role does not contain any profile or objects.
Can some one tell me which objects do I need to add to this role in order to use the Work Center System Monitoring?
Thank you very much!
regards
Thom

Hi Thom,
Most Work Center Roles are delivered without assigned roles.
The Work Centers are using the standard roles of SAP Solution Manager
Please see the updated [Security Guide SAP Solution Manager 4.0|http://service.sap.com/~form/sapnet?_SHORTKEY=01100035870000673252&_SCENARIO=01100035870000000112&_OBJECT=011000358700007187872005E] on page 24 for an overview of relevant roles on Solution Monitoring.
Best regards,
Ruediger

Materials / work centers associated with routing

Hi,
I need to develop a report on materials and work centers that are associated with a routing. How can I obtain the required information? Could someone please tell me if there is a table that I can pick the data up from using ABAP or query.
Also, are there any standard reports for displaying what materials / work centers are assigned to routing? Thanks.
Regards
Edited by: Khan Awkhan on Nov 23, 2008 8:05 PM

Hi Ashik,
Thanks for right input. If I had posted this thread I would have given full points to you.....
What kind of user are you Khan.... You should give points to Ahok and close the thread that will increase one good no. is resolved threads of SDN....... Else bring your problems that will be answered by PP experts.... I'm damn sure about it.....
Anyways thanks to you too as you at least posted this thread so that I got solution from it though it is indirect,,,,,,
Best Regards,
Abu Arbab

Main Work Centers

Hi,
Would like to know what exactly main work centers are ? How are they different from regular (operational) work centers ?
Is any configuration different for creating main work centers as compared to work centers ?
What is the hierarchy 'option' in the work center creation used for ? Is there a hierarchical relationship between Main work centers and work centers as far as comfiguration is concerned .
Appreciate any help.
Thanks,
Kingfischer

Dear King Fischer,
There are types & cat if we need to sepatre work centres in the customerisation if it needed normally it does not need in PM.
But in large detail planning etc. It may be used by business.
Following are the extracts for difference as per SAP.
The Main Work Center
The main work center must be entered in the order header, whereupon its master data is copied into the order as a default.
During internal processing, the main work center is also used as a default for the performing work center.
In addition to the main work center, you can create a specific employee, who has been represented in the Human Resources (HR) component with their own master record, as Person responsible.
The Performing Work Center
In addition to the main work center, you can create a specific employee, who has been represented in the Human Resources (HR) component with their own master record, as Person responsible. You can also assign other employees to an operation in the Requirement assignment.
The performing work center is managed in the operation data for the order. It is proposed as a performing work center for the operations in the order. Since capacities are assigned to the performing work center and costs assigned using the activity type, the performing work center is required primarily for capacity planning, scheduling and cost determination.
It is also possible to create operations without entering a performing work center. A control key, which is not linked to a cost center or an activity type, must then be assigned to these operations. It may be that the operations are simply used for documentation purposes, for example, operations that only contain safety instructions or specifications for the production/resources tools to be used. Operations without a specified performing work center are also used in external processing.
The Work Center as Production Machine
The work center as production machine is managed in the location data for the technical object of an order. It is only entered if the technical object at which maintenance work should be executed is a machine in Production.
Since machine capacities are assigned to the work center as production machines, the work center as production machine is required primarily for capacity planning of the machine, for example, non-operational periods for the machine must be planned as effectively as possible.
http://help.sap.com/erp2005_ehp_03/helpdata/EN/d7/45f364b10811d2a5e30060087a7a74/frameset.htm
Ramesh

Hi could someone help me please ? Ive just bought the new ipad and want to put some movies on it. I have already converted some movies using handbrake and tried to transfer them to my ipad and it just wont work. ive tried drag and drop and everything

Hi could someone help me please ? Ive just bought the new ipad and want to put some movies on it. I have already converted some movies using handbrake and tried to transfer them to my ipad and it just wont work. ive tried drag and drop and everything

bluztoo wrote:
Haven't really used any of them including VLC - actually use netflix on the ipad more than anything. I was able to drop an mp4 into imovie on my ipad and see it there. This was something I had shot as avhcd and converted with turbo.264. Played fine. Probably not what you want for a movie player though.
Well, turbo.264 is indeed very nice to have - even for converting full-sized movies. (Nevertheless, TechRadar's latest roundup (see http://www.techradar.com/news/software/applications/6-of-the-best-video-converte rs-for-mac-1074303 ; also linked from another roundup at http://www.iphonelife.com/blog/87/benchmark-excellent-multimedia-converter-handb rake-vs-commercial-apps ) has shown it's still worse than HandBrake in most respects.)
All H.264 files (assuming they are H.264 level 4.1 or lower) are compatible with the built-in Videos app.
bluztoo wrote:
Those of you who use other players, what do you reccomend? Just curious.
It entirely depends on your needs. The top players (AVPlayerHD / ProPlayer, It's Playing, GoodPlayer) all have different strengths and weaknesses. I myself use It's Playing the most as I convert everything into MP4 and simply love the DSP's (brightness / volume / saturation boosting). (Its software decoders are definitely worse than those of AVPlayerHD / ProPlayer; however, MP4's are played back from hardware.)

Routings and Work Centers Transfer using ALE

Similar Messages

Maybe you are looking for