Infotype 1000, Position data IDOC is not getting created via RBDMIDOC

Hi All,
We are using PFAL styandard HRMD_A message type, while executing RBDMIDOC with message type HRMD_A, all the infotypes data IDOC is created except Infotype 1000 Position(S).
The same is (Infotype 1000, position IDOC is created in dev server) but the same is not getting created in Quality and Prod.
Can any one suggest the same, what could be the error.
Thanks.

Hi,
You need to check in your filter settings in BD64 for your corresponding distribution model, if you have included IT1000 for PD objects such as O, C, S. After adding this filter group, you have to distribute the source system into the target system (Edit > Model view> distribute). In the target system, you have to generate partner profiles (environment> generate partner profiles).
Hope it helps,
Christine

Similar Messages

Mapping Issue: Target IDoc structure not getting created properly

Hi Experts,
I am stuck with a strange problem in my mapping. It is a M:N scenario mapping where we have multiple IDocs in source as well as in target.
For example, in source Queue-1 I am getting values as [SUPPRESS, true, true, true, true] and in the in source Queue-2 I am getting the values as [1,2,3,4,5]. I used MapWithDefault function to match the number of values in both the queues but in the target IDoc the node (say TMPN) is created only 4 times because of the condition put at the target node. So, the target node should have values as [1,2,3,4] but it gets values as [2,3,4,5] because the first target TMPN node is not created in the first target IDoc. I can provide you with the skeleton of the map. Hope this will give you a fair idea. Let me know if you require more details.
1. Target Structure:
    IDoc - No TMPN Node
    IDoc - 1 TMPN Node
    IDoc - 2 TMPN nodes
    IDoc - 1 TMPN node
Condition put on target TMPN_Node ---> (created only 4 times due to condition)
2. Mapping Skeleton:
Values coming from Q1 (SUPPRESS, true, true, true, true) --->
                                                                                \===>FORMATBYEXAMPLE+SPLITBYVALUE==> TMPN-F0 [2]
                                                                                /                                                                              TMPN-F0 [3]
Values coming from Q2 (1,2,3,4,5) -
>                                                                               TMPN-F0 [4]
                                                                                TMPN-F0 [5]
Where F0 is the field which is created when TMPN Node is created. So, if TMPN gets created 6 times, the F0 gets created 6 times.
Please let me know if there is an alternative to this problem. How can I have values as [1,2,3,4] in field F0 instead of [2,3,4,5]

hi,
i got the email.
as i can see your mapping seams to be rigth, but there is sometrhing i dont get. in a previuos post you said:
I am stuck with a strange problem in my mapping. It is a M:N scenario mapping where we have multiple IDocs in source as well as in target.
For example, in source Queue-1 I am getting values as SUPPRESS, true, true, true, true and in the in source Queue-2 I am getting the values as 1,2,3,4,5. I used MapWithDefault function to match the number of values in both the queues but in the target IDoc the node (say TMPN) is created only 4 times because of the condition put at the target node. So, the target node should have values as 1,2,3,4 but it gets values as 2,3,4,5 because the first target TMPN node is not created in the first target IDoc. I can provide you with the skeleton of the map. Hope this will give you a fair idea. Let me know if you require more details.
1. Target Structure:
IDoc - No TMPN Node
IDoc - 1 TMPN Node
IDoc - 2 TMPN nodes
IDoc - 1 TMPN node
lets asume you define as default value "1"
now, the result of the formatByExample taking the example you sent to me is:
1,T1,T2,T3,T4 without context change. and the result of the function splitByValue should be what you are specting.
but its something that is not clear still,
could you post the result of the mapWithDefault? i think your problem is there.
Rgds
RP-.

SRM: Sourcing - PO not getting created via sourcing

Dear SRM-ers,
I am facing problems while creating PO in the backend system via the sourcing cockpit.
My scenario is that when an approver SC enters the Sourcing cockpit, the user should be able to assign a vendor and proceed with creating a PO in the backend (without the bidding process).
When i click on the Create PO option i get an error, that 'some documents could not be generated or contain errors.'
Similarly in the application monitors the error is   "Shopping cart 1100000204 (PO 7000000055): BBP_BD 002 An exception has occurred"
When i try to debug this via bbp_pd transaction, the details that seem fishy to me are:
SRM          Purchase Requisition Document Type
BUS2012          Follow-On Document Object Type in Backend Sy
7000000055     Follow-On Document Object ID in Backend
The BUS2012 is a object ID of PO and the Document type that is getting populated is for PR (does this even matter?).
However, my current configuration is
SRM PR type (backend), SRM (PO type backend), and SRM BSA value.
PR
Number ranges 70 700000000-799999999 internal --> SRM
                       70 700000000-799999999 external --> Backend
PO
Number ranges 70 700000000-799999999 internal --> SRM
                       70     7000000000     7499999999 --> Backend for SRM PO
                        75     7500000000     7599999999 --> Backend for ECPO
Define Objects in Backend System:
50000006     *     QAS600     3 Always external procurement     2 Purchase order if item data complete, otherwise purch. req.
Sourcing for Product categories:
30WLDC001     QAS600     3 Sourcing Carried Out for Items Without Assd Source of Supply
This is the category i am mkaing the Shopping cart for.
Warm regards.
Osayed Rehman

Hi
Again I am telling you have configured
Sourcing for Product categories:
30WLDC001 QAS600 3 Sourcing Carried Out for Items Without Assd Source of Supply
that is why P.O is created
SPRO path-SRM server-Sourcing for product categories
Please change to Sourcing never carrired out (or ) change according to your scenario.and try
Regards
G.Ganesh Kumar

Checks not getting created VIA FPY1

Hello All,
I am trying to create checks using FPY1. Even though the entries to Customer contract accounts are being posted correctly there are no checks being created (I am not concerned about printing the checks). When I look at the posted document the check number field is blank. All through the FPY1 run there is no error in the logs. The client I am working in was recently copied over and as a result so did the payment medium do I have to create a new payment medium or does the payment medium that was copied over will do. I tried creating payment medium via FBPM but it does not show up in FPY1> Environment > Payment Medium >Payment Medium Variant. Please guide.
Regards,
Reena

Hi Reena,
There are couple of things that needs to be checked, it is a configuration issue
check the below things before running the FPY1 again
1) Has check lots been configured
2) Is payment medium format ( check ) created
3) Is payment medium variant created (program SAPFKPY3)
If you have both the payment medium format and variant for it and then assign them in FPY1 and you should be able to see the check numbers.
thanks,
VR

For the new delivery type created the Idoc is not getting triggered

Hi All,
I am facing the following problem:
For every outbound delivery getting created we have an Idoc which creates the file(sending the outbound delivery details), this file is sent to a system where the picking & packing of the goods happen. This process seems to be working fine for all the existing delivery types, but now we created a new delivery type for which the Idoc is not getting triggered.
Would like to understand what setting are we missing because of which the Idoc is not getting created for the new delivery type.
The Idoc being used is: DESADV01
Message type :DESADV
Thanks,
Geeta

I believe your existing idocs are created through a output type on the delivery ? if yes, probably you need to configure an existing output type / create a new output type for your new delivery type...

Infotype 0573 not getting created

Hi All,
We have an R/3 transaction created for leave application and this is showcased in EP6.0 portal as an Internet Service. Now, when we apply for leave using this application through portal, for certain employees, infotype 0573(Absence infotype for Australia PS) is not getting created but 2001 gets created. When we try doing the same through PA30 or through the R/3 transaction itself, everything is going on fine. Only while applying through portal, this issue occurs. This was working fine in EP5.0 portal.
Can anyone suggest a way to sort this issue? Any help will be rewarded.
Thanks and Regards,
Leena

Hi Leena
Please note that the function module HR_ABSENCE573_REQUEST_PBS was internally used by SAP only for corresponding ESS services of Leave administration Australia Public sector functionality. The behavior for the function module is as expected, when
called from corresponding ESS services. Further the same function module is currently not enabled to be used outside the same. Also there are no further issues with creation of Infotype records in 0573 and 2001 (which are consistent) from PA30 (Maintain Master data).
Hence would you please check if you are using the standard function module
HR_ABSENCE573_REQUEST_PBS and perform an operation. As I mentioned Function module HR_ABSENCE573_REQUEST_PBS which is currently being used by ESS services for Leave administration.
Regards,
Jun Wu
SAP HCM Support team (AU/AU-PS)

Infotype not getting created using FM HR_INFOTYPE_OPERATION

I am trying to create infotype 210 from user exit ZXPADU02 using below code.
DATA : v_return TYPE bapireturn1,
           v_return1 TYPE bapireturn1,
           v_return2 TYPE bapireturn1,
           v_key TYPE bapipakey,
           v_return3 TYPE bapireturn1.
p0207 = gt_p0207.
MOVE-CORRESPONDING p0207 TO p0210.
p0210-infty = '0210'.
p0210-begda = p0207-begda.
p0210-taurt = 'PR'.
p0210-txsta = '01'.
p0210-amtex = '0'.
CLEAR : p0210-aedtm.
CLEAR : p0210-uname.
CLEAR: v_return,v_return1,v_key.
CALL FUNCTION 'BAPI_EMPLOYEET_ENQUEUE'
    EXPORTING
      number        = p0210-pernr
      validitybegin = p0210-begda
    IMPORTING
      return        = v_return.
IF v_return IS INITIAL.
    CALL FUNCTION 'HR_INFOTYPE_OPERATION'
      EXPORTING
        infty         = '0210'
        number        = P0210-PERNR
        subtype       = 'PR'
       objectid      = p0210-objps
       lockindicator = p0210-sprps
        validityend   = P0210-ENDDA
        validitybegin = P0210-BEGDA
       recordnumber = p0210-seqnr
        record        = P0210
        operation     = 'INS'
      IMPORTING
        return        = v_return1.
ENDIF.
CALL FUNCTION 'BAPI_EMPLOYEET_DEQUEUE'
    EXPORTING
      number        = p0210-pernr
      validitybegin = p0210-begda
    IMPORTING
      return        = v_return.
But infotype 210 is not getting created.
When i check it from PA30, i get error
"No data stored for Residence Tax Area in the selected period"
Can anyone tell me what is the problem here.
Full points will be rewarded.

HI,
check the value coming on the screens are properly.Use DIALOG_MODE as foreground and check whether all fields getting populated.
Check any default values need to be populated.
Regards,
Manoj.

Production version is not getting created using ALE-IDOC

Hi all,
Am using BD10 to transfer the material from sending to receving system.All the views are geting sent successfuly accept the production version tab data of MRP4 view.The segment is available in the standard IDOC.But prodction TAB is not getting created at receving system .Please help to resolve this issue.
Thank you.

Hi Sanu,
BD10 Send Material..
the reason might be Production tab is not created is the segment is not a mandatory..
and the data is not populating for that fields.
if the segment is not madatorty and data is not available for the fields in the segment ..the prodction TAB will not be created ..
Regards,
Prabhudas

IDOCS Error - Not getting processed automatically

Hi All,
We are loading hierarchy for a Product from R/3 system using the standard datasource.
When we execute the info package, IDOCs are not getting processed automatically.
We are facing the below error message.
Error when updating Idocs in Business Information Warehouse
Diagnosis
Errors have been reported in Business Information Warehouse during IDoc update:
No status record was passed to ALE by the applicat
System Response
Some IDocs have error status.
Procedure
Check the IDocs in Business Information Warehouse . You do this using the extraction monitor.
Error handling:
How you resolve the errors depends on the error message you get.
But when we goto BD87 and process the IDOCs manually, these are getting posted and the hierarchy is loading.
Can someone please guide me on what is the issue with the IDOCs and how to make them to post automatically.
Thanks in Advance
Regards,
Sachin

Hi,
This will happen due to Non-updated IDOCu2019s in the Source system i.e., occurs whenever LUWu2019s are not transferred from the source system to the destination system. If you look at RSMO of the status tab, the error message would appear like u201CtRFC Error in Source Systemu201D or u201CtRFC Error in Data Warehouseu201D or simply u201CtRFC Erroru201D depending on the system from where data is being extracted. Sometimes IDOC are also stuck on R/3 side as there were no processors available to process them. The solution for this Execute LUWu2019s manually. Go to the menu Environment -> Transact. RFC -> In the Source System from RSMO which will asks to login into the source system. The u201CStatus Textu201D for stucked LUWu2019s may be Transaction Recorded or Transaction waiting. Once you encounter this type of status Execute LUWu2019s manually using u201CF6u201D or Editexecute LUWu2019s(F6).Just keep on refreshing until you get the status u201CTransaction is executingu201D in the Production system. We can even see the stuck IDOCu2019c in Transaction BD87 also.Now the data will be pulled into the BW.
Hope it helps a lot.
Thanks and Regards,
Kamesham

FI - Interface triggerring multiple idoc is not getting posted

Hi all,
I have a scenerio, where I am receving data from SAP PI, which calls standard idoc ACC_DOCUMENT03 and which posts FI Document.
now, the problem is interface trigger's 2idoc with seperate number with same message type and same idoc type, but both the idoc are not getting posted and show's error like 'No currency line exists for line item 0000000001' and so on.
But the same idoc, when i proccess indivisually get's process gets posted successfully.
I have also done implementation in function module IDOC_INPUT_ACC_DOCUMENT.
As an abaper, I am not able to understand problem to take corrective steps.
Thanks & Regards
shashikant

hi,
if the IDoc is stuck in a qRFC queue means that the message did not reach the pipeline to be send to R3 so, anything in wrong at PI side.
please, go to SMQ2 and check whats happening. to know the queue name check the SXMB_MONI, select the proper message and scroll rightto the proper colum.
let us know.
Rodrigo P-.

SRM PR is not getting created in ECC backend

Hello Experts,
We are running SRM 7.0 with SRM-MDM Catalog, we are using SRM for shopping. We do have PI 7.11 running in the Environment as well.
We are on ECC 6.0 with Ehp 4.0
Purchase Order:
However we can see the PO creating successfully using PI.
Question, in the SRM table (BBP_FUNCTION_MAP), we see the object type: BUS2012 for ERP 4.0 has adapter name: /SAPSRM/CL_SOA_ADPT_PO_CRT_ERP for when creating PO. Please see teh screen shot.
is this the reason that we need PI?
Purchase Requisition:
PR Creation is not working:
PR is not getting created in the ERP, PR uses Object type: BUS2105, Adpater CL_BBP_BS_ADAPTER_RQ_CRT_470 for ERP 4.0 System type, can you please tell me if the adapter is correct for ERP 4.0 system type?
I also have a question to ask:
1) Where did you see that PR/PO was send to PI System (PI1)? My understanding is that since ERP amd SRM are 2 ABAP Systems, why we cannot send the PR/PO directly to ERP system from SRM? Why do we need a middleware(PI) in between for this process? We should be able to USE BAPI function to do it correct?
Please advice.
Thanks
Kumar

yes, i could see a PR number with all this additional details as below.
Table   BBP_PDBEI
CLIENT                       453                                                              Client
GUID                         4CAEFA58EB9D005CE1008000AC1C2031                                 Globally Unique identifier
BE_LOG_SYSTEM                QA1400                                                           Logical System of Logistics Backend
BE_OBJ_ITEM                                                                                Follow-On Object Item in Back-End System
BE_OBJECT_TYPE               BUS2105                                                          Follow-On Document Object Type in Back-End System
BE_OBJECT_ID                 2000000167                                                       Follow-On Document Object ID in Back-End System
BE_REFOBJ_TYPE                                                                                Reference Object Type in Back-End System
BE_REFOBJ                                                                                Reference Object in Back-End System
BE_REFOBJ_ITEM                                                                                Reference Object Item in Back-End System
BE_REFOBJ_SBITM                                                                               Reference Object Sub-Position in Backend System
BE_REFOBJ_TYPE2                                                                               Reference Object Type in Back-End System
BE_REFOBJ2                                                                                Reference Object in Back-End System
BE_REFOBJ_ITEM2                                                                               Reference Object Item in Back-End System
BE_REFOBJ_FYEAR2             0000                                                             Reference Document Object - Fiscal Year in Back-End System
BE_STGE_LOC                                                                                Storage location
BE_PLANT                     2016                                                             Plant
BE_BATCH                                                                                Batch Number
BE_VAL_TYPE                                                                                Valuation type
BE_MOVE_REAS                 0000                                                             Reason for Movement
BE_EXPERYDATE                00000000                                                         Shelf Life Expiration Date
BE_PUR_GROUP                 206                                                              Purchasing group
BE_PUR_ORG                   2000                                                             Purchasing organization
BE_CO_CODE                   2000                                                             Company Code
BE_DOC_TYPE                  CLRQ                                                             Purchase Requisition Document Type
BE_ACCREQUIRED                                                                                Account Assignment for Logical Backend Required
BE_SP_STK_IND                                                                                Key for Special Stock Section
BE_INFO_REC                                                                                Number of purchasing info record
BE_MOVE_TYPE                 201                                                              Movement type (inventory management)
BE_PACKNO                    0000000000                                                       Package number
BE_INTROW                    0000000000                                                       Internal line number for limits
BE_ITEM_TEXT                                                                                Short Text of a Service Purchase Order Item
BE_PO_PRICE                  1                                                                Price from Backend
BE_UNLOAD_PT                 200                                                              Unloading Point in Backend
BE_DEL_IND                                                                                Deletion Indicator in Backend Documents
BE_TRACKING_NO                                                                                Requirement Tracking Number
BE_COND_TYPE                                                                                Condition Key
BE_COND_STEP                 000                                                              Level Number
BE_COND_COUNTER              00                                                               Condition counter

File not getting created in a different server

My requirement.
I have written a code in the BI system and now need to write an empty file (say a.done)in a directory /interfaces of PI system.
I wrote using open data set and close data set however the file (a.done) is not getting created in the PI system even though the directory /interfaces exist.
When I give any directory of that of BI system ,the file(a.done) is getting created i.e the file is getting created on the same server and not on the different server.
Is there any function module or any other way for the file to get generated in the PI system.
Please explain with an example.
Regards,
Vish

Try to use search FTP in se37 or checkout the below FM
CALL FUNCTION 'EPS_FTP_MPUT'
EXPORTING
    RFC_DESTINATION            =
*   FILE_MASK                  = ' '
*   LOCAL_DIRECTORY            = ' '
*   REMOTE_DIRECTORY           = ' '
*   OVERWRITE_MODE             = ' '
*   TEXT_MODE                  = ' '
*   TRANSMISSION_MONITOR       = 'X'
*   RECORDS_PER_TRANSFER       = 10
*   MONITOR_TITLE              =
*   MONITOR_TEXT1              =
*   MONITOR_TEXT2              =
*   PROGRESS_TEXT              =
* IMPORTING
*   LOCAL_DIRECTORY            =
*   REMOTE_DIRECTORY           =
*   LOCAL_SYSTEM_INFO          =
*   REMOTE_SYSTEM_INFO         =
* TABLES
*   FILE_LIST                  =
* EXCEPTIONS
*   CONNECTION_FAILED          = 1
*   INVALID_VERSION            = 2
*   INVALID_ARGUMENTS          = 3
*   GET_DIR_LIST_FAILED        = 4
*   FILE_TRANSFER_FAILED       = 5
*   STOPPED_BY_USER            = 6
*   OTHERS                     = 7
IF SY-SUBRC <> 0.
* Implement suitable error handling here
ENDIF.

BP not getting created while creating employee

Hi,
When I Hire an employee a BP should be created for it. It used to happen earlier in the system but after we moved to another system this is not working. Can someone please let me know the necessary config for this?
I've the following settings:
HRALX ONUMB = 2
HRALX OSUBG = MD
The MD number range is from 90000000 to 9999999999. Should this number range be internal or external?
When I use the HR_SYNC_PERSON report for an employee I get the error as
"Determination of connections to object 'BP' of 'CP' '50000201' failed"
"Object of type 'US' with ID '1122' does not exist or is inconsistent"
"Determination of connections to object 'BP' of 'O' '50000101' failed" etc
Also I need to upload the employee master data using LSMW and BP does not get created with LSMW also? Is there some specific config while using LSMW?
Please help.

Whenever you are uploading employees using LSMW, you need to run program HR_SYNC_PERSON.
Pls refer to the following thread for further info:
Assignment: Business partner for person '50000029' is not unique
Regards,
Dilek

WBS Elements not getting created in ECC Project System from CRM 7.0

Dear all,
We are trying to integrate SAP CRM 7.0 with SAP ECC-PS module. The objective is to bring in the marketing plan and elements data from the CRM system, and to create the corresponding WBS in project system. We have done most of the configuration as recommended by SAP in both the systems, and we see that the BDOCS are getting generated and sent to the ECC system. The following steps have been successfully completed:
1.       Set up the RFC connections between the two systems
2.       Selected the connection type as Middleware in CRM system.
3.       Installed the cProject Add on in CRM box.
4.       Created a project scenario (with project and network profiles) in the PS system and assigned the same in the CRM system.
5.       The Project Scenario in PS config has the same name as the Project Type in CRM config.
6.       Created and released the campaign ids being created in the CRM system.
As already mentioned, we can see that the BDOCS are coming to the ECC system and are getting stored in BDOC_TRACK table. However the issue is that the corresponding WBS elements are not getting generated in the ECC system. Is there anything that that we are missing in the ECC box which would trigger the WBS element creation?
Request you all to share your inputs which would be immensely beneficial for us in achieving this integration.
Thanks and Kind Regards,
Aditya Shrivastava

Hello Aditya,
We too are facing this issue.. if you have resolved the issue could you please let us know the solution ?
Some inputs related to our system,
We have upgrade from CRM 4.0 to CRM 7.0 SP07 and R/3 backend system is on 4.7 SP27, earlier we have completed the upgrade on sandbox without any issues which was upgrade to CRM 7.0 SP04 but with SP07 we are facing the problem of WBS Element not getting created in R/3.
Your help is highly appreciated.
Thanks & Regards,
Sumukh Kapoor.

Attachment not getting created in PI from CRM

Hi Everyone,
I am trying to create attachments in PI from CRM but it is not getting created there. I am executing the following steps:
By default I am getting the attachment data in Binary format so I am using this function module to convert it into XSTRING format.
          CALL FUNCTION 'SCMS_BINARY_TO_XSTRING'
                          EXPORTING
                     input_length = lv_input_length
                     first_line   = lv_first_line
                     last_line    = lv_last_line
                   IMPORTING
                     buffer       = lv_xbuffer
                   TABLES
                     binary_tab   = file_content_binary.
   2. Then I am getting the server context and the protocol.
                       obj_server_context = cl_proxy_access=>get_server_context( ).
                       obj_attch_protocol ?= obj_server_context->get_protocol( if_wsprotocol=>attachments ).
* Assign File naame to STRING Variable
                       lv_name = lv_filename.
* Attach file to the service response.
                       obj_attachment = obj_attch_protocol->get_attachment_from_binary(
                                  data = lv_xbuffer
                                  type = if_ai_attachment=>c_mimetype_pdf
                                  name = lv_name ).
                       APPEND obj_attachment TO t_prx_attach.
                       obj_attch_protocol->set_attachments( t_prx_attach ).
   3. Then I am using a proxy class which has Input and Output structures for sending data to PI and getting the response respectively. And then in the end I am calling the proxy and passing the structures.
     With this I am unable to see the attachmenmts in sxmb_moni transaction. Please help.

Hi Gurus,
Can you please help with some pointers on this.
I have used below links as reference for coding.
Link 1 :
http://help.sap.com/saphelp_nw04/helpdata/en/a7/3b2a2d45a34a23b75e3b18745c63bc/content.htm
Link 2:
http://scn.sap.com/community/pi-and-soa-middleware/blog/2012/10/19/abap-proxy-protocols-use-cases-and-examples
After setting attachment(Method SET_ATTACHMENTS) i am not getting any exceptions,but still i am not able to see any attachment created in SXMB_MONI.
Thanks in Advance,
Manil.

Infotype 1000, Position data IDOC is not getting created via RBDMIDOC

Similar Messages

Maybe you are looking for