Segment E1EDL24 not generating

Hi,
While posting the GRN from MM and sending it to SRM,the segment E1EDL24 which contains the inbound delivery, material etc.. details is not generating in MM in the IDOC STPPOD.
Please advise ASAP.
Thanks,
Manu

if it runs successfully but no trace files generated, you can open SR at oracle support regarding this issue.

Similar Messages

Express document "Art. segments not generated correctly" received from aut

Art. segments not generated correctly
dear all
i created an article in MM41. while doing the listing in WSM3 this error is occurring same plant i was created artilces and listed also but today it is showing this error msg . Can u please suggest me how to solve this?. i showed to my tech team they told me to check in configuration settings?. is their any problem with config ?.
Note:- Article segments were not created in full
The data is stored in the log 00000000000000049016 file
1741001 No entry in key field in distribution chain segment for article 1741
Possible causes:
- Reference article was not maintained in full
- Inconsistent maintenance of article
Possible actions:
- Maintain reference data
- Call transaction WSPK to edit the faulty segments
thank you
RK

i clearly mentioned what was the error occured for me agian ur asking quetion means i can't tell m . i created an article in mm41 while doing the listing in wsm3 that time this error is occuring if u can solve i will be happy
thank u
rk

Idoc all segments not generated

Dear Everyone,
                      I am doing File to Multple IDOC scenario.Multiple Idocs are generated successfully but only one segment fields are coming.I used 5 segments while doing mapping.
E1KNA1M
   E1KNVVM
     E1KNVPM
E1KNB1M
     E1KNB5M.
             only E1KNA1M segment turned into GREEN,remaining 4 segments are still showing as GREY color only.but i mapped some fileds in all those 4 segments with source fields.IDOC also generated without errors.I need to get remaining 4 segments fields also.I couldn't find what the error is.Any help would be appreciated.
Thanks in Advance
Vinay

Hi,
To get generate the fields of a segment and the segment occurence is 0...unbounded
then you need to map the source field based on which the no of target segment has to be occured. if there is no such source field then need to map the constant to the target segment so that fields under that segment will get generated in the target mapping..
Hope this clears your query..
Regards
Rajesh

Adding field in standard IDOC Segment E1EDL24

Hello Friends,
I have an urgent requirement that I have to extend IDOC segment E1EDL24 with two fields PABNR and LFSNR.
When I tries to change the segment in WE31, it shows an error message that you can only modify the segments of customer namespace and cannot modify Standard IDOC Segments.
Can we modify the standard IDOC segments, and if yes, how can we modify the standard IDOC segments. Please clarify.
Points will be rewarded generously.
Regards,
Navin

Hi Naveen,
We cannot Modify the Standard segments. But we have to Create a new Segment and Add these fields.
Then Create an Extended Idoc type
Implement User Exits in Outbound And Inbound ..
This is the Complete Steps and Info on this...with an Example...
Enhancing ALE
For example, if in an outbound interface you find that the IDOC type does not contain all the data you need to pass to the other system, you can extend the IDOC to accommodate the additional fields and enhance the ALE function modules to populate the fields. Similarly, if in an inbound interface, there is additional data that needs to be posted to the R/3 application, you can extend the IDOC type to have additional fields populated by the external system or translator or the other R/3 system and then enhance the inbound ALE function modules to post the additional data to the R/3 application.
let us use the SAP Customer Master application as an example. Specifically, letâs focus on the IDOC extension and ALE function module enhancement of IDOC type DEBMAS02 and message type DEBMAS (Customer Master) and the IDOC reduction of message type MATMAS.
IDOC EXTENSIONS
Letâs first look at the concept of IDOC extension. SAP delivers Basic IDOC types such as DEBMAS02, MATMAS02, ORDERS02, and WMMBID01. By extending the Basic IDOC type, you are actually creating a new IDOC type. You create a new segment with the additional fields. This new segment has to be associated with one of the existing Basic IDOC segments. Then you create a new extension type, which is associated with the Basic IDOC type. This results in a new IDOC type. In order for ALE function modules to relate to this new IDOC type, the IDOC type is linked to the corresponding message type.
Note that you should not add fields to existing segments but should create a new segment and associate it with an existing segment. This, in a nutshell, is the process of creating IDOC extensions.
In our example, the Basic IDOC type DEBMAS02 is used to communicate Customer Master data to the SAP Customer Master application. Even though the application has a screen to enter and store a contact personâs business address (see Figure 1), DEBMAS02 does not have a segment or fields that communicate the contact personâs business address. If your business requires that this business address be communicated to the other system through the ALE interface for Customer Master, then you have to extend the DEBMAS02 IDOC type, and enhance the corresponding ALE function module.
In DEBMAS02 the contact person fields are present in segment E1KNVKM and the business address of the contact person is stored on the SADR SAP table. You need to create a new segment, Z1SADRX, that is associated with E1KNVKM. This will be done in the process of creating an extension type ZDEBMASX. This extension type will then be associated with a new IDOC type, ZDEBMASZ. IDOC type ZDEBMASZ will be linked to message type DEBMAS for Customer Master. The final step in the IDOC extension process is to check the new objects. This check also verifies the structural integrity of the IDOC type. Letâs look at each of these steps in more detail.
1. Create an Extension Type and a New Segment.
Determine the fields on table SADR that you are going to provide for in the new segment Z1SADRX. You need fields for name, street, city, region, and country to give the business address of the contact person. You also need fields for the address number. ADRNR is a field in SAP tables such as SADR that uniquely identifies the address of an entity. This field is cross-referenced from other tables to the SADR table to obtain the full description of the address. Because this is an IDOC type for master data, the first field of the new segment will be MSGFN. The message function field informs the receiving system of the action to be taken for that particular segment. In the code that you write for populating the new segment, the value of the message function is the same as that of the parent segment E1KNVKM. In all, you will have 12 fields in segment Z1SADRX (see Table 1).
To create an extension type and new segment:
Use transaction WE30 or from WEDI go to Development -> IDOC types.
Enter ZDEBMASX for Object Name.
Choose Extension Type.
Click on Create.
You will see a pop-up screen. Choose Create New, and enter a description. For version 4.x, enter DEBMAS02 in the Linked Basic Type field. Enter.
You will see a screen with ZDEBMASX and its description in the first line. Click on this line, and press Create. For version 4.x, expand the tree of segments, and place the cursor on E1KNVKM.
You will see a pop-up screen. Enter E1KNVKM as the reference segment. Enter.
For 4.x, press Create after placing the cursor on segment E1KNVKM.
You will see a line appear with E1KNVKM hierarchically below ZDEBMASX, with a description "Customer Master contact person (KNVK)."
Click on this line and press Create. You will receive a message indicating that the new segment being created will be a child segment of E1KNVKM. Enter. A pop-up box appears for the new segment.
Enter Z1SADRX as the segment type, 1 for Minimum, 1 for Maximum. Leave Mandatory segment unchecked. These entries imply that there is only one Z1SADRX segment for every occurrence of the E1KNVKM segment, and also that this segment is not mandatory. Note that if the parent segment is not mandatory, then the child segment should not be mandatory, because this could result in a syntax error during the creation or processing of the IDOC.
For 4.x, you must first create the IDOC segment Z1SADRX (Iâll explain why in a moment) from the menu path WEDI -> IDOC -> Development -> IDOC Segment.
Click on Segment Editor.
On the next screen, click on Create.
Enter a development class for the object. Enter.
This will take you to the screen for segment definition. Enter a description for the segment. Enter the field name, data element, and the data element documentation name. In most cases, all three fields may have the same values. If you are using a field in the segment that is not present in the ABAP/4 data dictionary, you must first create the domain, data element, field, and appropriate documentation before using it in the new segment.
Enter these three columns for all 12 fields. Save.
Click on Generate/Activate, F3 to step back.
From screen Maintain Segment, go to Segment Type -> Release. A checkbox now appears beside the segment definition Z1SADRX (see Figure 2). Check this box. Save.
Save again to store the descriptions of the segment, F3 to step back.
Save the extension type.
It is possible to have several new segments with relevant Basic IDOC type parent segments in a single extension type. However, you can form only one IDOC type based on a single extension type.
2. Create an IDOC Type.
The next step is to create an IDOC type by associating the extension type that you created with the Basic IDOC type. This is a simple process:
From transaction WE30 or WEDI go to Development -> IDOC Types.
Enter ZDEBMASZ for Object Name.
Click on IDOC Type.
Click on Create.
Enter DEBMAS02 for Basic IDOC type.
Enter ZDEBMASX for extension type.
Enter a description.
Enter.
You will see a display of the composite IDOC type with all segments, including Z1SADRX (see Figure 3).
It is possible to associate only one extension type with a Basic IDOC type for a given IDOC type. However, you can have multiple new segments in an extension type.
3. Link IDOC Type to Message Type.
The next step is to link the new IDOC type to its corresponding message type. This is important, because this relationship is referenced in the partner profile parameters where you specify the message type and IDOC type to be used for that particular representative system. To link the message type:
Use transaction WE82, or from WE30, go to Environment -> IDOC Type / Message Type, or from WEDI go to Development -> IDOC Type -> Environment Î IDOC Type / Message Type.
Click on Display <-> Change.
Click on New Entries.
Enter DEBMAS for message type.
Enter DEBMAS02 for Basic IDOC type.
Enter ZDEBMASX for extension type.
Enter your SAP R/3 release number for Release.
Save.
This data is stored on the EDIMSG table and is accessed by several ALE processes to relate the message type to the IDOC type.
4. Check the IDOC Type.
Before checking the IDOC type for consistency, it is important to perform another step that releases the extension type to the IDOC type:
From WEDI go to Development -> IDOC Types -> Extras -> Release Type, or from transaction WE30 go to Extras -> Release Type.
For the Object Name ZDEBMASX and radio button Extension Type, click Yes.
The extension type has now been "released."
You canât edit the extension type once itâs released. To cancel the release for further editing or deactivation, go to WE30 Î Extras Î Cancel release. The final step in the IDOC extension process is checking the validity of the IDOC type:
From transaction WE30 or WEDI go to Development -> IDOC types.
Enter ZDEBMASX for Object name.
Click on Extension Type.
From the Development Object menu select Check.
Repeat the operation for IDOC type ZDEBMASZ.
A check log will be generated for each run with details of correctness or errors (see Figure 4).
In some situations it is possible to receive errors during the check process, especially segment length errors. The incorrect IDOC segment can be repaired and corrected by executing program RSEREPSG. This program checks the formal consistency and repairs incorrect segments. In test mode it will generate a log of formal correctness for the specified segment only. For the program to repair segments in normal mode, the underlying IDOC structures (DDIC structures) must be active. This program rectifies the lengths of the DDIC structures and not the fields themselves. RSEREPSG can also be used to change the person responsible for the object and the release flag.
Menu paths may vary slightly depending on the release/version of SAP R/3, but the procedures and the principles are the same.
ALE FUNCTION MODULE ENHANCEMENTS
Having extended the IDOC type to contain additional fields for an inbound or outbound application, you now want to enhance ALE function modules for populating the additional segment on the outbound or applying the additional segment data on the inbound application.
The core working code for ALE processes for a given application area is always encapsulated in ABAP/4 function modules. These function modules are associated with such control information as message types and process codes. So the ALE process checks this control information and derives the name of the function module to invoke for that particular IDOC processing from certain database tables. These function modules contain objects known as customer functions, which can be considered SAP Enhanced user exits. A function module is called at a particular point during the processing of the main program or function module, and it can be used to influence data processing at that point by adding code to the customer function. The customer function behaves like a normal function module and has import and export parameters, tables (internal tables) statement, and exception processing. Unlike a conventional user exit, customer functions give you the ability to modify only data available to you by the function moduleâs parameters and internal tables. While most ALE/EDI function modules are supported by customer functions, there are ALE/EDI processes that still use conventional user exits. There are a few ways to determine which function module to enhance for a given message type/process code:
For master data distribution, from SALE go to Extensions -> Master data distribution -> Setup additional data for message types. Search for message type DEBMAS in this example. You see an entry for DEBMAS associated with function module MASTERIDOC_CREATE_SMD_DEBMAS. This data is stored on table TBDME. The function module names for all master data message types follow this pattern: MASTERIDOC_CREATE_SMD_messagetype. This function module calls another function module of name MASTERIDOC_CREATE_DEBMAS or MASTERIDOC_CREATE_messagetype. Search for the words customer function, and you find several hits that can be used to add code to the function module.
From WEDI got to Control -> Inbound process codes -> Inbound with ALE service -> Processing by function module (transaction WE42), or from WEDI go to Control -> Outbound process codes -> Outbound with ALE service -> With function module (transaction WE41). There will be function modules associated with the process codes. For inbound, the function modules usually follow this pattern: IDOC_INPUT_messagetype: for example, IDOC_INPUT_CHRMAS for inbound characteristics master.
Use transaction WE57 or from WEDI go to Development -> Message/Application Object. The entries list the function module, Business Object, message type, and IDOC type that are used for inbound ALE/EDI interfaces.
Customer functions are not specific only to ALE and EDI but also to all programs/modules in SAP R/3. Customer function is a SAP enhancement component; the other two types are menu and screen enhancements.
All customer function exits are maintained in SAP enhancements and are found by using transaction SMOD. After executing transaction SMOD, pull down (F4) on the enhancement name field, and execute again. This provides you with a list of all SAP enhancements available. SAP enhancements are grouped by development class pertaining to an application area. Choose Application development R/3 SD master data distribution for development class VSV to lead to a screen that lists VSV00001 as an enhancement (see Figure 5). Press Component +/- to display its function exit components. There are four possible components listed, all of which are function exits (and are function modules) that are called from the ALE function modules in the form Call Customer Function Î001â. This is a special occurrence of the ABAP statement Call. Go to item Exit_SAPLVV01_ 001, which you need to enhance for the Customer Master outbound example of an IDOC extension. In the ALE-function module MASTERIDOC_CREATE_DEBMAS, the statement CALL Customer Function 001 is translated in the background to call component EXIT_SAPLVV01_001. Although this function exit can be edited using transaction SE37, you will use a simpler approach.
When you use SAP enhancements and their components, you manage them with an SAP object known as a project, which is like an envelope containing the selected enhancements and their components. A project can be used to control the execution of components and to transport them to other clients and instances in SAP. Basically, the process involves creating a project, including enhancements and components that are to be enhanced, editing the components, and then activating the project. The following process creates a project for our example Customer Master IDOC extension:
Execute transaction CMOD.
Enter name of project, say CSTMAST1.
Click on Create.
Enter a description of the project.
Save.
Click on SAP Enhancements.
Enter VSV00001 for Enhancement.
Save.
Once youâve created the project, edit the function exit components and activate the project. Remember that the code in the function exit enhancement will execute only if the project is activated. In fact, this is a convenient SAP enhancements feature, whereby the work in progress (developing code in the customer function) will not affect users of that application. When the code is completed, the project can be activated so the enhanced functionality takes effect. It can also be deactivated for maintenance.
As mentioned earlier, customer functions (function exits) are embedded in ALE function modules and can be used to influence the creation and modification of IDOC data on an outbound application or to post additional or modified IDOC data to an inbound R/3 application. Function exits are similar to regular function modules, with import/export parameters, tables (internal tables), and exceptions.
The two important factors to consider while developing the customer function are:
1. The point in the ALE function module where the function exit occurs
2. The data made available by the customer function that can be modified or posted to the R/3 application, based on the direction.
Because some function modules have several customer functions, it is critical to choose the function exit best suited for that particular enhancement. Do not attempt to perform activities that the function exit is not designed for. The importance of this point is illustrated by the following description of enhancing function modules for outbound and inbound ALE interfaces.
Outbound interfaces. In an outbound ALE interface you use function exits (customer functions) to populate additional segments created by an IDOC extension or to modify the existing IDOC data segments as per business requirements. Previously, you identified that enhancement VSV00001 has a component EXIT_SAPLVV01_001 (function exit), which can be used for populating the additional data segment Z1SADRX that you created in the IDOC extension ZDEBMASX (IDOC type ZDEBMASZ, based on Basic IDOC type DEBMAS02). You also learned that the ALE function module that calls this function exit is MASTERIDOC_CREATE_DEBMAS, which has a statement Call Customer Function 001.
Browse the function module MASTERIDOC_CREATE_DEBMAS using transaction SE37. You will find that this customer function is invoked for every segment of IDOC type DEBMAS02. In fact, the function exit is called soon after the creation of an existing segment has been populated with data and appended to the IDOC data table (internal table). Also, the function exit is exporting the message type, IDOC type, and the segment name and is importing the IDOC extension type. It is also passing the IDOC data internal table. This indicates that the ALE function module is allowing you to populate additional segments for every existing segment and modify the existing segmentâs data.
Letâs write ABAP/4 code to accomplish the task of populating IDOC segment Z1SADRX with a contact personâs business address:
From SE37, display function module MASTERIDOC_CREATE_ DEBMAS.
Find Customer Function 001.
Double-click on 001.
The function EXIT_SAPLVV01_001 will be displayed.
Double-click on INCLUDE ZXVSVU01.
You will be asked to create a new include object. Proceed as desired.
Enter code (as in Listing 1).
Be sure to perform a main program check (Function Module -> Check -> main program) and extended program check (Function module -> Check -> Extended check).
Now that you have extended the IDOC and enhanced the ALE function module based on the requirements for the contact personâs business address on the Customer Master, letâs test the interface. You should create a logical system and define a port for this interface. You should also configure the Customer Distribution Model to indicate that message type DEBMAS is being distributed to this logical system. The only difference in configuration between a regular outbound ALE interface and an enhanced one is the partner profile definition. While maintaining the outbound parameters of the partner profile, make sure the IDOC type is ZDEBMASZ. The fields for Basic IDOC type and extension type are automatically populated with DEBMAS02 and ZDEBMASX, respectively.
To maintain the contact personâs business address of a customer:
Use transaction BD12 or from BALE go to Master Data ->Customer -> Send and send that Customer Master record by executing the transaction after filling in the relevant fields such as customer number, message type, and logical system.
Use transaction WE02 or WE05 to verify the IDOC created. You should see the new segment Z1SADRX populated with the correct data.
With SAP releases below 4.5B, you cannot capture changes to business address through change pointers because a change document object is not available for capturing business address changes, and also earlier releases have not been configured to write change documents for a contact personâs business address. If you would like this functionality, you can either create change document objects, generate function modules to create change documents, and perform ALE configuration to tie it in, or make a cosmetic change to the contact person screen data while changing the contact personâs business address so that it gets captured as a change to the Customer Master. Subsequently, the ALE enhancement that you performed captures the contact personâs business address.
Inbound interfaces. The process for enhancing inbound ALE interfaces is similar for outbound, with a few exceptions; specifically in the coding of customer functions (function exits) for the ALE/EDI function modules.
The first step is to create an IDOC extension for the specific Basic IDOC type by adding new segments at the appropriate hierarchy level: that is, associated to the relevant existing segment. Populate the data fields on the new segments with application data by the translator or external system/program before importing them into the R/3 System. Then, find the ALE function module that is invoked by the inbound processing. By browsing through the code or reading the documentation on the function exit enhancements using the SMOD transaction, identify the function exit in which you should place your code. The technique used in the code to post the additional or modified IDOC data to the application can vary based on the application rules and requirements, the data available at that point in processing, and the application function modules available to update the application tables. It is important to search first for application modules that process the data and see if they can be called within the function exit. If the additional data in the extended segments in specific to a custom table or resides in nonkey fields of a single or small set of tables, you may be able to update it directly by SQL statements in the function exit. This approach should be carefully evaluated and is certainly not highly recommended.
Another option is to use Call Transaction from within the function exit to process the additional data. For example, in the case of message type WMMBXY for inbound goods movements from a warehouse management system, the standard interface creates batches for materials, but does not update its characteristics. In such a case, you can use Call Transaction MSC1 to create the batch and assign characteristic values to it from within the function exit provided.
Error handling is a very important consideration when making enhancements to inbound ALE/EDI objects. In ALE and EDI inbound processing, workflow is used for handling errors at different levels such as technical and application. If workflow has been configured for the interface, the error messages and workflow items flow to the inbox of the named recipient(s).
It is also critical to enhance the workflow that handles notifications of the inbound ALE/EDI process. In most scenarios this is not a very difficult task because SAP lets you influence the workflow parameters and messages in function exits (customer functions). You typically do this using flags and message codes to trigger certain workflow actions. If you conform to the status codes and flags stipulated for workflow processing, the enhancement could be error-free and seamless. In the case of an inbound IDOC with an extension, you should populate the EDIDC fields IDOCTYP (new IDOC type) and CIMTYP (extension type) accordingly.
Reward if Helpful

COPA document not generated though after billing and accounting generations

I have an issue with one instant.
For some reason COPA document is not generated even though billing and accounting document were created. Found no errors in simulation using KE4ST. The billing item details has all the PA segment characteristics.
COPA documents were created for entries made befor and after this particular one.
Also we have COPA documents for the product with the same customer and different customers.
Our system is 'SAP ERP Central Component 5.0'

Thanks Ajay for the quick response.
Cost element category is correctly maintained.
Condition types are mapped.
COPA is in use for more than 4 years.
Able to simulate COPA document for the Billing document without errors.
We do have COPA documents created before and after this particular transaction.
As you said raising OSS message with SAP.
Thanks

Custom Segment is not appearing in orders05

Hi ,
I am trying to extend IDOC type ORDER05.I have followed all the steps But even then segment is not appearing after i generate IDOC and test in we02.
The two fields has to extended in EKKO and same has to extened in ORDER02 at the time PO creation.
This is the requirement. Right now iam not passing any data in the custom segment but i have done all the initial configuration..
Idoc also generated succssfully..but its having my custom segment..Pls advice

Yes, that include need to be created. By double clicking on it you will get a prompt to create the object (provided you have developer access), choose yes and you should be able to create the include and put a break point on it.
In IDOC_OUTPUT_ORDERS function module that creates the outbound ORDERS05 IDoc.
--> EXIT_SAPLEINM_002 will be called repeatedly for each IDoc segment while the IDoc is still building
--> EXIT_SAPLEINM_011 will be called once for the whole IDoc, once SAP finished building it
So yes, you can use any of these user exits to manipulate the output IDoc.
Also, the break point won't get triggered when output type is set to trigger immediately (dispatch time 4) when you issue the output from ME22N / ME23N, because the IDoc will be triggered asynchronously in this mode by the system and not in your session, so your session break points are ineffective.
What you need to do is go into the ME22N output page (Click Messages on ME22N screen, select the condition type in yellow color (not yet processed), click on "Further data"and set "Dispatch time" to 1 (Send with periodically schedule job). After doing this issue the output (by saving the PO etc). This will mean that the output IDoc is not triggered immediately.
Now put the break point in the suggested user exit.
Come to SE38 and execute RSNAST00 program, give "Output application" as "EF", object key as your PO number (format it with leading zeros for full 10 digits) and enter your output type. Run it and then you will see that your break point is hit.

Trial balance not generate profit center wise

Dear All,
Please suggest,
I am generate the trial Balance "S_PL0_86000030 - G/L Account - Balances " with profit center wise, system not generate the trail balance with profit center wise because profit center or business segment is not updated the system.
I generate the trial balance at company code level same t-code, system generate the trail balance but system show the column of profit center or business place "not assigned"
It is possible to update the profit center and business segment table.
Pleases suggest to solved my problem
Regards

Hi, have you activated PC scenario?

COPA: PGI not generating COPA document

Hi
I am using costing based COPA.. I know that in this type of COPA, the Cost of Sales [COS] GL account is not created as Cost element.. But, I am fed up of reconciliation between FI and COPA due to timing gap between PGI and billing..
So, I created the COS a/c as cost element category 1, In Okb9 made the PSG (Prof Segment) as default CO Object and also mapped this Cost element to a Value field in FI PA transfer structure
When I do PGI, system generates only FI doc and Controlling document.. No COPA document is generated
In FI doc, system populates the PSG in COS line item and in Controlling doc, the Object Type is REO (Reconciliation Object)....however, no COPA doc is generated despite this
Can I generate a COPA doc at the time of PGI?? I know that it will duplicate COGS in COPA, but I am taking care of that by mapping to a different value field
I tried using the cost element categories 1 and 12 both.... But the COPA document is not getting generated
Any inputs??
Regards, Ajay
Edited by: Ajay Maheshwari on May 25, 2009 1:35 PM

Hi Santosh
I agree to what you have said.. But, I want to take it to COPA by way of creating it as cost element and doing the settings in OKB9... Also, I mapped it to a value field in PA Trf Str
Is it possible that using the record type B system generates a COPA doc
Why I feel it shud/can get generated is that when we change the std cost, system posts revaluation if inventory exists.. This revaluation amount can be taken to COPA by way of same settings in OKB9 and PA transfer Str..
Similarly, I am trying for PGI.... Dont know why system is not generating COPA doc?
Any ideas whether it can be technically done??
Ajay

BDOC and Segment are not valid

Hi All,
We are facing an issue in the BDOC creation, We have a created a query BDOC (Mobile Application Modifiable ) in the CRM System, Activated it. Generated the Metadata in the Client console. We have used the same bdoc and segment for the document generation.
However In the Mobile client when the document is generated we are getting an error "BDOC and Segment are not valid" please let us know.

Hello
Could you please apply the notes 1161839 and 1164220 which has fixes for that issue.
After applying the fixes, register the dll Genservicewrapper.dll present in
<<Drive>>:\Program Files\Microsoft Visual Studio 8\Common7\IDE
After that, register UGM.dll preesnt in %mobilerootdir%\Bin.net folder.
Now open MAS and sync the BDOCs.
Best Regards
Shankar

Income tax is not generating on Bonus for second time through off cycle

Dear All,
I have an issue related to bonus. We have given bonus off cycle in the month of August 16th income tax was deducted on bonus amout. Now again mgt is giving bonus through offcycle in the month of November 10th but the problem is Income tax is not getting calculated in this month for bonus. We have checked the calculations every thing is fine.
We have created 1 wage type for 1st time bonus as Special Bonus and 2nd time we have created another wage type as Diwali bonus. We have done configuration same as 1st wage type special bonus for Diwali bonus wage type.
Let me know where it went wrong.
Rgds,
Prasad

Hi Narendra,
Thanx for the response, i tried the above but not generating WT/460. can you explain the logic.,
Changed BON5 to BON3
created new Tax code ZTDR from STDR
Assigned Bonus WT ( in 0267) to ZTDR in Table T7INT9
didn't understand why /401 or MTDR or 9TDR
Thanks
Sanm

Miro line item not generated

Dear All,
I have facing one issue at the time posting in MIRO.
I post one of migo doc in date 03/01/2010 , the entry is:( with same material )
Post key   description amt                               curr.( USD)
89              Stk.RM -IMP                                     32100.00
96              PL.VND.RM.IMP GR/IR                     32100.00
40              Purchase RM-IMP                            32100.00
50              Purchase offset.                             32100.00
And Miro Posting on date 23/03/2010
Post key   description amt                               curr.( USD)
31           xyz Vendor                                    32100.00
86           PL.VND.RM.IMP GR/IR                    32100.oo
89           Stk.RM -IMP                                    -
40           Purchase RM-IMP                          -
50           Purchase offset.                           -
But when I post for another po in migo on date 03/01/2010
Post key   description amt                               curr.( USD)
89              Stk.RM -IMP                                     76800.00
96              PL.VND.RM.IMP GR/IR                     76800.00
40              Purchase RM-IMP                            76800.00
50              Purchase offset.                             76800.00
and miro posting on date 19/02/2010
Post key   description amt                               curr.( USD)
32            yz Vendor                                       76800.00
86           PL.VND.RM.IMP GR/IR                      76800.00
89           Stk.RM -IMP                                      Line item not generated
40           Purchase RM-IMP                             Line item not generated
50           Purchase offset.                              Line item not generated
Can any one tell why line item not generated for miro posting .
Regards
Milind

Hi,
The extra line items will be generated when there are any exchange rate diffrences are there then only shows.
Other wise it wont show those extra line items
Please check group currency , global currency etc. for your extra line items

XML Publisher question - Not generating a valid XML file

I am working through an Oracle document that walks you through creating an XML Pub report. I am using HCM 8.9, Tools 8.49.15 and it has XML Pub installed and I have the Microsoft plug-in installed
I have created a query and have downloaded an rtf template and now am on a page where you enter your data source and then click ‘Generate’ for the sample data file. I did it and it created ‘PERSONAL_DATA_PAY.XML’ which is created from a PS Query. However if I click on ‘PERSONAL_DATA_PAY.XML’ it generates a blocky text file that is not an XML file and I can’t go any further.
Do you know why it’s not generating a valid XML file when I click on 'generate'?
Thanks
Allen H. Cunningham
Data Base Administrator - Oracle/PeopleSoft
Sonoma State University

You mean to say that you create a new data source by specifying Data Source Type as 'PS Query' and Data Source ID as your query name, you are not able to generate a valid XML file (by clicking on Generate link).
did you cross check your query by running it?
On field change of Generate link, PeopleSoft uses PSXP_RPTDEFNMANAGER and PSXP_XMLGEN app packagaes and query objects to create the file
It should work if you query is valid..

Inspection Lot not generated, with MIGO 561

Hello All,
Please help me with this issue.
WHen i do MIGO with 561, inspection lot is not generated.
So there is a setting in spro, if we check that, inspection lot wont be generated.
So now in my IDES, i tried to uncheck that box.
When i save this setting, I get the following error.
"Fill table key for table T156Q only up to position 010".
Please help with this issue.
Regards,
Piyush

To load initial inventory in Quality stock and release it using Inspection lot UD, use movement type 563 instead of 561.
With 561 movement stock is directly posted to un-restricted status. So there is nothing to be released from Quality stock.

Customized Seeded report to XMLP report but its not generating output file?

I want to customize "Dunning Letter Print from Dunning Letter Generate" Report, which is called from "Dunning Letter Generate" Report
Steps i followed to Customize reports are.
1. Changed output format to xml for "Dunning Letter Print from Dunning Letter Generate" Report.
2. Ran report to generate xml data and using xml data created RTF file
3. Registered data definition and template with code and short name same which is ARDLP_NON_SRS
Now while i am running report its completing normal, but its not generating output file giving Error like –
"Unable to find Published Output for this request"
“No Output File Exist for Request No - xxxxx”
No Idea why its not picking template, Can anyone help me in this?
Using:
Oracle Applications : 10.0.5.2,
MS Word 2007
Thanks,

I am not giving the solution, providing you a hint..
This is the query you need to satisfy,
SELECT NVL(R.DESCRIPTION ,CP.USER_CONCURRENT_PROGRAM_NAME)
FROM FND_CONCURRENT_REQUESTS R, FND_CONCURRENT_PROGRAMS_VL CP,XDO_DS_DEFINITIONS_B XDS
WHERE ( ( FND_PROFILE.VALUE('CONC_REPORT_ACCESS_LEVEL') = 'U'
AND R.REQUESTED_BY = :$PROFILES$.USER_ID ) or
( FND_PROFILE.VALUE('CONC_REPORT_ACCESS_LEVEL') = 'R'
AND R.RESPONSIBILITY_ID = :$PROFILES$.RESP_ID ) )
AND R.PROGRAM_APPLICATION_ID = CP.APPLICATION_ID
AND R.CONCURRENT_PROGRAM_ID = CP.CONCURRENT_PROGRAM_ID
AND XDS.APPLICATION_SHORT_NAME=
( SELECT APPLICATION_SHORT_NAME
FROM FND_APPLICATION
WHERE APPLICATION_ID=CP.APPLICATION_ID)
AND XDS.DATA_SOURCE_CODE = CP.CONCURRENT_PROGRAM_NAME
AND R.OUTPUT_FILE_TYPE='XML'
AND R.STATUS_CODE not in ('E', 'D', 'T', 'X')
ORDER BY R.REQUEST_ID DESC
Go to system profiles and query for 'Concurrent:Report Access Level', responsibility you need and modify the profile name accordingly....

MRP is not generating any schedule line in my vendor's scheduling agreement

Hello all,
My question is: why the MRP is not generating any new line in my vendor's scheduling agreement?
This is the scenario:
I have created a vendor's scheduling agreement with transaction ME31L
I have created a customer's scheduling agreement with transaction VA31 and those characteristics:
- Forecast scheduling lines
- JIT scheduling lines
- MRP to DS type assigned to type C: Requirements according to forecast delivery/Deliveries according to JIT
I have run MRP with transaction MD01
MRP is generating some purchasing requistions, not purchase orders because we have set up a release strategy which requires 2 approvals, but those purchasing requests are not generating any new line in the vendor's scheduling agreement.
Any idea why it could be? Please do not hesitate to ask for further explanations. Thank you

Hi,
Check if stock is available for the material in that plant.
Also check the requirement date for the material and compare it with the planning horizon for that plant.
Check your material master MRP view.
Create source list(for material and plant in question) with MRP indicator 2.
Thanks and Regards,
Maheshwari

Segment E1EDL24 not generating

Similar Messages

Maybe you are looking for